Changelog
Every release, newest first. Downloads: GitHub Releases.
[0.5.0-beta.5] - 2026-11-09
Accuracy behind VPN and SASE clients. The engine is routemap-engine 0.9.0, which has its own list.
Added
- A notice when the route goes through a tunnel adapter: "Traffic to this target goes through [adapter]. The map shows the path through it, not the direct internet path." It links to help, remote agents and RIPE Atlas reverse traces. Adapters are read from your system on every run, with the names your system reports; no product names are built in. An adapter the system does not clearly describe is "unclassified", named only in the Interface section of the route summary and in exports, with no notice.
- An origin warning when the origin is on Auto and the system's default route goes through a tunnel adapter, with a link to Settings > Origin. A tunnel that carries only some targets gets no warning. The origin is never changed for you and nothing new is looked up.
- Probe interface, in Settings > Trace and as
-i/--interfacewith--list-interfaces: Automatic (the system route) by default, then every adapter your system reports. It applies to Trace, Paths and Watch. After a run on a chosen interface hop 1 is checked against it, and the result says if the probes were redirected or if it could not tell. If the adapter has no route, the run stops and says so; nothing is sent another way. - A one-time notice when a physical adapter is chosen while a tunnel is up.
- A TCP interception check on Paths over TCP (Windows). A connection completed or refused at TTL 2 or less marks the TCP results unreliable, unless the target is on a local subnet or an ICMP echo reaches it at the same TTL. The export names the condition. A TCP and ICMP difference at hop 1 is reported only when both answered.
- Help > Using Route Map behind a VPN or SASE client, the same text as the guide.
Changed
- JSON exports gain optional
interface(kind and name) androute.paths.interception. The export stays format version 5; 0.5.0-beta.4 reads these files and ignores the new keys (tested with its released reader). This computer's addresses and gateways go in only when you tick the box in the Export dialog, or pass--interface-addresses. - PDF reports name the interface and carry the notices. PNG exports say when a route went through a tunnel.
- PRIVACY.md and Help > Privacy state that adapters, addresses and gateways are read locally and never sent.
[0.5.0-beta.4] - 2026-10-29
Watch and a change of the system clock. The engine is routemap-engine 0.8.2, which has its own list.
Fixed
- Watch dropped a healthy cycle when the system clock changed (routemap-engine#24, reported on Bluesky by sasame-mcp.bsky.social). A time sync or setting the clock by hand while probing ran normally was recorded as a sleep gap, and that cycle was left out of the statistics. A gap is now only sleep, suspend or a stopped app, measured on a clock that keeps counting while the computer sleeps; the cycle is kept. Placement and the map were never affected.
Changed
- Clock changes are said where gaps are: the live note and the PDF ("Clock changed at 14:02:07 (+5 s); this cycle was kept."), a "Clock changes" row in the PDF, and a note under the CLI table. The live plot runs on the same clock as the gap check, so a kept clock change leaves no blank stretch and no overlap; exported sample times stay on the wall clock.
- "Clock check off": where that clock cannot be read, the session falls back to the older check (a clock change may then show as a gap) and says so once, with the reason, in the live note, the PDF, the CLI and the JSON.
- The JSON session has
clock_steps(at,seconds; negative when the clock was set back) andclock_fallback(null, or the reason). The export stays format version 5; older versions of Route Map ignore both. - The guide,
docs/cli.md, the FAQ, the limitations, troubleshooting, the in-app Live help and the site say what a gap is and that a clock change is not one.docs/cli.mdand the guide said Watch's JSON was format version 4; it is 5.
[0.5.0-beta.3] - 2026-10-26
Paths on Windows. The engine is routemap-engine 0.8.1, which has its own list.
Fixed
- Paths on Windows when a probe's port is taken. Each Paths flow had a fixed source port between 40000 and 50009, a range that overlaps the ports Windows hands out to other programs' connections, and Windows refuses a port another program holds (WSAEACCES 10013). That flow's probes never left the computer, its paths were missing, and 20 refusals in a row ended the run with "this computer refused to send probes". Each flow now uses a port Windows assigns and keeps it for its later probes; if another program takes it in between, the flow gets one new port and is probed again from hop 1. Whether the port ranges Hyper-V, WSL 2 or Docker Desktop reserve cause the same refusal is not known; a range reserved with netsh did not.
Changed
- The Paths note says why a probe could not be sent, by error name and code ("20 probes could not be sent by this computer (WSAEACCES 10013)"), in the window, the CLI and the PDF, and names a flow probed again on a new port. The JSON has
local_failure_reasonsandflows_restartedunderroute.paths. - Settings > Agents and the guide: a Windows server needs routemap-engine 0.8.1 or later for Paths.
[0.5.0-beta.2] - 2026-10-26
A security update; nothing else changes. The engine is still routemap-engine 0.8.0.
Security
- certifi 2026.10.19 in the app (was 2026.7.22), for GHSA-6q48-6c7w-9gw2: the list of certificate authorities the app trusts no longer has emSign ECC Root CA - G3, whose intermediate CAs had their private keys compromised. The app checks every HTTPS connection it makes against this list: online lookups, the DB-IP download and the update check.
Changed
- Build, site and test tools, none of them in the app: Pillow 13.0.0 (41 advisories) for the site's images and its tests; brotli 1.2.1 (GHSA-9v8h-qqgm-4m35) for the font test; filelock 4.2.1 (GHSA-v4x8-3wr5-3wq8, GHSA-9vhv-jxww-xfm5, GHSA-567q-5qvw-pf92) for the tool that writes each release's SBOM; setuptools 84.1.0 (GHSA-xmj3-9gf7-h52w) for the build. The GitHub Actions that upload, download and set up Python move to their newest patch releases, pinned by commit.
[0.5.0-beta.1] - 2026-10-26
"Investigate": DNS timing, port tests and traces from your own servers. The engine is routemap-engine 0.8.0, which has its own list.
Added
- DNS timing. Every trace times the lookup of its target, A and AAAA, through your system resolver and through each resolver you add in Settings > Probes (IP addresses only, none by default), with the response code, whether the answer is authoritative and its TTL; "not stated" where a resolver does not say whether it answered from its cache. The summary names the address traced and the system resolver's time; a DNS section above the hop table, in the PDF and in the JSON lists every lookup. Added resolvers are asked only while Online lookups are on, and not with
--offline. Settings > Probes can time the lookup once per Live cycle (off by default). - One resolution per trace. The target is resolved once and the trace, Paths and the port test go to that address; traceroute, tracert and mtr are given the address, so the address shown is the one traced.
- Port tests (Ports next to Paths,
routemap TARGET --ports [LIST]): one TCP connection to each port in Settings > Probes (443, 80, 22, 25, 53 and 3389 by default) on the traced address, open (with connect time), closed or filtered, with a TLS handshake time for 443 and the ports marked; certificates are not checked. At most 32 ports, 4 at a time, no ranges: a reachability check for one target, not a port scanner. Next to a Paths run, an open port 443 says the target is up and the routers in between are what is silent. Off with every trace by default. - Remote agents (Settings > Agents, the From list next to Trace,
routemap TARGET --from AGENT): one Trace, Paths or port test run on a server you already reach with ssh, over your own ssh (-T,BatchMode=yes, a 15 s connect timeout, one connection, never retried, never in the background), mapped from the server. The server needs routemap-engine 0.8.0 for its user (pip install routemap-engine); Test connection reports its version and what it can probe. The server provider's first hops are hidden by default (no address, name or place), in the result, every export and the lines shown while it runs; Show first hops shows them. The agent is placed by a city you give, or from its public IP by a RIPEstat lookup made on the server. Placing the hops and every lookup happen on your computer. Ctrl+C on a remote run closes the ssh session at once (exit code 130). - Paths: the discovery stops after 5 silent hops (was 3), then asks the target at full TTL on each of the paths found, reached or not; a path answered only then is shown reached with its silent stretch marked. The heading says why the discovery ended and which address it probed. Over TCP (Windows), a hop where no TCP probe was answered gets one ICMP echo, and the heading says when the routers there do not answer TCP probes, or when the target answers ICMP but its TCP service only at full TTL (a firewall or load balancer in front of it is likely). When the target answered on some path, a path whose attempts all went unanswered shows "0 of 10" ("some servers answer fewer after the discovery's probes"); "not reached" means no path reached the target.
- Anycast destinations are placed. A destination that answered faster than its registered place allows is placed near you, Source "anycast, served from near X", counted from the last placed hop before it: bbc.com's Fastly address, registered in Montreal and answering in 8 ms from Manila, is placed near Quezon City. The summary uses the same words.
- Hops inferred from their neighbours. A hop no source places, between two hops placed in one city, is shown in that city with Source "inferred from neighbours" and a hollow marker, in the window, the PDF and the JSON (source
neighbours): Arelion's link to Plus.line, 62.115.153.153, between two Frankfurt hops, which DB-IP puts in Chicago. - Settings are kept across upgrades. Before a new version saves over the settings an older one left, it keeps them as
settings.previous.json; a settings or history file that cannot be read is set aside (.unreadable), never replaced by defaults, and the window and the CLI say so. The macOS build is checked to read 0.4.0-beta.2's settings from a fresh home folder. - CLI:
--dns,--resolver ADDR,--no-dns,--ports [LIST],--from AGENT.
Changed
- Export format 5 (the traced address, DNS lookups, port results and the agent). Formats 1 to 4 still open; 0.4.0-beta.2 says "Made by a newer Route Map" when it meets one.
- The PNG title names the traced address and the DNS time; it never shows port results.
- The PDF Paths table prints the differences all the paths share once, above the table, and each row only its own.
- Classifiers for Python 3.11, 3.12 and 3.13.
Fixed
- A hop several routers answered shows the router its name belongs to. Hop 11 to heise.de read "62.115.153.153, ffm-b16-link, not placed": the name was another router's, which is in Frankfurt by Arelion's site code.
- The test suite never writes to the real config folder. The isolation starts before any test is collected (a test module unpacked the ASN database there while being collected), and a run that changes the real folder fails.
- The site's figure check, Open Graph renders and consent banner test no longer touch the macOS keychain: headless Chrome starts with
--password-store=basicand--use-mock-keychain; without them a test run from a non-interactive context showed a "Keychain Not Found" dialog for every page rendered.
[0.4.0-beta.2] - 2026-10-12
0.4.0-beta.1 was tagged but not released: its check of Paths on a real Windows network failed (paths counted where only a silence differed, one address placed in two cities, the target repeated, 342 s for one run). This release has the fixes, with routemap-engine 0.7.1.
"Paths": the paths a load balancer spreads your traffic over, the route back via RIPE Atlas, and IPv6 end to end. The engine is routemap-engine 0.7.0, which has its own list.
Added
- Paths (a button next to Trace, Trace > Find Paths, Ctrl+Shift+T,
routemap TARGET --paths): finds the paths a per-flow load balancer can send your packets along, with Paris traceroute and the multipath detection algorithm's stopping rule at 95% confidence, and gives each path its own latency and loss to the target from ten pings of one of its flows. The map draws each path's branch in its own colour with its letter, the hop table gets a Paths column and a sub-row per router where the paths part ways, and the Paths list under the table shows each path's flows, where it differs, and its RTT and loss; choosing one shows it alone. Per-packet balancing is named and does not make paths. The count is "at least": some balancers do not spread every kind of probe. At most 20 probes a second and 1,500 per discovery (the pings included; Settings > Trace can lower the budget), 64 flows, 3 silent hops. ICMP probes on macOS and Linux, TCP probes to port 443 on Windows (10 version 2004 or later), no administrator rights; the method is shown in the window, the CLI, the PDF, the PNG and the JSON. - Reverse trace via RIPE Atlas (next to the summary, Trace > Reverse Trace via RIPE Atlas,
routemap TARGET --reverse --publish-my-ip): a connected probe in the target's network, or its country, nearest the target and never in your own network, traces back to your public IP. Forward and reverse are shown side by side, aligned by network, the differing rows tinted, and the reverse route is drawn dashed with diamonds where the directions split and rejoin. It costs 60 credits; nothing is scheduled when no probe is found. - Reverse traces ask the probe to wait 2 seconds for each reply (RIPE's default is 4), so a path whose routers stay silent takes about half as long; a router slower than 2 seconds counts as silent. A trace usually takes 1 to 3 minutes. The answer to Atlas's final TTL 255 probe is shown as the next hop with the note "TTL 255 probe", and Atlas hops are checked against the probe's own position (a few kilometres), not the 300 km allowed for an origin found from a public IP.
- OVHcloud's backbone is placed from OVH's own router names (engine 0.7.0), where the IP database put it in the wrong cities.
- Consent for reverse traces. A reverse trace publishes your public IP address as the target of a public RIPE Atlas measurement. Before the first one Route Map says so and asks you to agree; nothing runs without that. Every reverse trace shows the probe, the IP that will be published and the cost first. Settings > RIPE Atlas > Withdraw consent stops them at once. The command line never uses the window's consent:
--reverseneeds--publish-my-ipon the same command. - IPv6 everywhere. The built-in prober traces IPv6 on Windows, macOS and Linux; Watch runs over IPv6 (0.3.0 refused it); macOS falls back to
traceroute6, the other tools get-6. Settings > Trace > IP version (Automatic, IPv4 only, IPv6 only) and-4/-6on the command line choose the family for a host that has both; the origin lookup and RIPE Atlas follow it. - The PNG and PDF carry the paths and the reverse trace; the PDF has Paths and Reverse trace sections.
- The download page links
SHA256SUMS.ed25519next toSHA256SUMSandSHA256SUMS.asc.
Changed
- Export format 4. Every export from this version is format 4 (paths, a reverse trace and the address family); 0.3.0-beta.1 says "Made by a newer Route Map" when it meets one. Formats 1 to 3 still open.
- Addresses in special-purpose blocks follow the IANA registries row by row (engine 0.7.0), the same on every Python.
Fixed
From the Windows checks on a real network (ODIN), before release:
- A Trace hop the next hop rules out is not placed: a router answering slowly between two Frankfurt hops is no longer drawn in Chicago, and the countries no longer read DE > US > DE. One address has one placement in a run, in Trace and in Paths.
- The hop table shows a cut cell's full text on hover, and shortens at the end ("Frankfurt am Ma…"), never in the middle.
- Paths: the summary gives each AS path and country list with the letters of the paths that take it, and the target per path ("10 of 10 answered: A C · not reached: D") instead of one trace's loss sentence over the merged table. The map legend uses the same words, and a path that never reached the target says so with the last hop that answered.
- Paths: a hop several routers answered shows "N routers", their ASN only when they share it ("mixed" otherwise), no RTT averaged across them, and each router's own place and source.
- Paths: a discovery stopped at its probe budget says so in its heading.
Not in this release
- "Splits from" names the town where a path parts from the one listed before it. It should show the router address where both routers are in the same town, and compare against the most similar path rather than the one listed before.
[0.3.0-beta.1] - 2026-10-10
"Live": continuous trace and ping plot. The engine is routemap-engine 0.6.0, which has its own list.
Added
- Continuous mode. Watch (next to Trace), Trace > Watch Continuously (Ctrl+Shift+W) or
routemap --watch TARGETprobes one target again and again, mtr style, with the built-in ICMP prober: every hop once per cycle, spaced evenly across the interval. Per hop: sent, received, loss, last, best, average, worst and jitter (standard deviation), accumulating over the session. Pause (P, outside text fields), Resume, Stop (Ctrl+.) and Reset counters (no shortcut). - Ping plot under the table for the selected hop and the destination, over 5 minutes, 15 minutes, an hour or the whole session (keys 1 to 4), with lost probes and path changes marked so colour is never the only cue; it uses the chosen RTT palette, the colour-blind one included.
- Path changes with cycle and time: a hop's routers compared over the last 10 cycles with the 10 before, so ECMP alternation is never a change; a hop appearing or disappearing and the destination moving are changes too.
- Loss follows the 0.2.0-beta.6 rule over the session's own figures: intermediate-only loss is ICMP rate limiting, destination loss is real.
- Sleep and suspend leave a gap in the plot and the statistics, never loss, and the session notes it.
- The map is drawn from the first full cycle; later cycles only add hops or routers not seen before. Geolocation is not repeated per cycle.
- Limits in Settings > Live, following mtr: 1 s per cycle by default and never faster (mtr's default and its floor without root), at most 30 probes a second, a 1 s wait per reply, 5 silent hops past the last that answered, and a session that stops after 1 hour by default and 8 hours at most.
- Export and compare: a session exports to PDF (the mtr table, the changes and gaps, one plot per hop for the whole session) and to JSON format version 3 (
session: per-hop statistics, plot data, changes, gaps), reopens from History or File > Open Trace, and compares like a trace, with the session's average as each hop's RTT and its loss as the hop's loss. - CLI:
routemap --watch TARGETwith--interval,--countand--duration, an mtr-style table that redraws on a terminal, and with--jsonthe version-3 export at the end. Values outside the limits are refused with the reason. - History keeps stopped sessions, 50 MB of them at most together; past that the oldest sessions are dropped first (Settings > Live says so).
- Accessibility: every live control is named; the bar announces a pause, the end of a session and path changes, not every tick; rows are read when focused; the plot's description summarises the range shown.
Changed
- JSON exports are format version 3. Version 2 files open as before; a file from a newer version is refused with a clear message.
- Files up to 8 MB are opened (was 1 MB), for an 8-hour session with its plot data. A session from a file is rebuilt like a route: every count, time and RTT checked, every list capped, the loss notes computed again.
Not in this release
- IPv6 targets in continuous mode (planned for 0.4.0). RIPE Atlas is never used for it.
[0.2.0-beta.6] - 2026-10-09
Housekeeping and usability. The engine is routemap-engine 0.5.0, which has its own list.
Added
- One-click update. Help > Check for Updates > Download and check fetches the file for this system from this project's GitHub releases into a folder only you can read, and checks that
SHA256SUMS.ed25519is a signature by the update key built into the app over the release tag andSHA256SUMS, thatSHA256SUMSlists the file once, and that the file's SHA-256 matches. Then it runs the installer (Windows), opens the disk image (macOS), opens the.debor.rpmin your software installer, or replaces a running AppImage in place and restarts. A failed check deletes the download and names the check. Traffic goes only to this repository's release files and GitHub's release-asset host; these downloads do not appear in the site's download statistics. Versions up to beta.5 still open the download in the browser. The GPG signature (SHA256SUMS.asc) is unchanged. - Atlas credits before every Atlas trace: your balance, what this trace costs and what is left after it, from RIPE's own figures. A key RIPE does not accept stops the trace with a button to Settings; a key without "credits read" hides the balance and still traces. The message for a key without "credits read" (RIPE's 403) is not yet tested against RIPE itself, only against a constructed answer; the unknown-key message (401) is.
- Help > Create Bug Report: a zip of version, commit, OS and settings, with every key and token and your set origin removed, and the last trace only if you tick it. Every file is shown exactly as it will be saved. Nothing is sent.
- A first-run tour of the origin, a trace, the map, the table, Settings and Help. Skip it with Esc; Help > Show the Tour brings it back. Settings from an earlier version count as having seen it.
- Accessibility: a colour-blind-safe RTT palette (Settings > Map > Colours), checked by simulating protan, deutan and tritan vision, with hot steps also drawn dash-dot; the map and the globe walked with the arrow keys, Home, End, Enter and Esc (Shift with the arrows pans); a name for every control and hop table rows read out in full.
Changed
- A RIPE Atlas trace costs 60 credits, not 30. RIPE charges a one-off measurement twice what a periodic one costs (https://atlas.ripe.net/docs/getting-started/credits). The figure in Settings and the Atlas dialog now comes from the engine.
- Loss that is only ICMP rate limiting is not reported as loss. Its Loss cell is greyed in the table and the PDF; the route summary, the PDF and the JSON export (
"loss") report only the loss that reaches the destination, and "unknown" when the destination never answers. - The Settings text asks for the "credits read" permission alongside "schedule a new measurement", for the balance.
- Every RTT colour meets 3:1 against land and sea (WCAG 2.1, 1.4.11) in both palettes and both themes. On the light map the grey is a shade darker (#7b8896, 2.98:1 before) and the amber is darker (#b67b06, 2.06:1 before); the dark map already passed. A test checks every colour and blend the map can draw.
Fixed
- With Atlas on but no key, Trace from a RIPE Atlas Probe opened Settings on the Map tab instead of the RIPE Atlas tab.
Dependencies
- cryptography 50.0.2 (with cffi 2.1.1 and pycparser 3.1) is back in the app, by hash, to check the update signature.
- fonttools 4.66.1 in the test lock.
[0.2.0-beta.5] - 2026-10-06
Fixes from a validation round on beta.3. The engine is routemap-engine 0.4.2, which has its own list.
0.2.0-beta.4 was not released: its Windows build failed, so the tag v0.2.0-beta.4 has no release and no files. Everything below was meant for beta.4; in addition, the release build now fetches the Dependency Walker that Nuitka needs on Windows itself, checked by SHA-256.
Security
- Engine 0.4.2: compressed answers no longer get past the 2 MB cap. In 0.4.1 the cap on answers from the online sources counted the bytes as they arrived, before decompression, so a small compressed answer could decode to hundreds of megabytes and exhaust the app's memory. The engine now asks every source for an uncompressed answer and refuses one that arrives compressed anyway, before decoding any of it. The app installs it from PyPI by hash, as before.
Fixed
- A malformed export ends in a clear error, never in a crash inside the window. Three kinds of route file got past the checks added in beta.3 and failed later, two of them while drawing: a number no route holds (an RTT, loss or distance far out of range), a place with a latitude but no longitude, and JSON nested too deeply to parse. Open, Compare with an Export,
routemap-cli --compareand the history file now refuse such a file and say where the problem is; a settings file nested too deeply falls back to the defaults. Exports and history files written by beta.1, beta.2 and beta.3 open unchanged. - Windows: upgrading an all-users install that beta.2 put in a chosen folder retires that folder. beta.2 let an install for all users go into any folder and put it on the machine PATH; since beta.3 such installs go into Program Files only, and the old folder and its PATH entry stayed behind. The installer now takes the old folder and its
binoff the machine PATH, deletes there only Route Map's own files (following no junction or symbolic link) and removes the folder once it is empty.
Changed
- Route Map is not on PyPI.
pip install routemapinstalls an unrelated project of the same name. The README and the download page now say that Route Map comes only from its GitHub Releases and getroutemap.app, and that its engine is theroutemap-enginepackage.
[0.2.0-beta.3] - 2026-10-05
Fixes from a security review of the app, the engine and the release path. The engine is routemap-engine 0.4.1, which has its own list.
Security
- Opened, compared and remembered routes are rebuilt before they are shown. A route export (File > Open, Compare with an Export, or
routemap-cli --compare) and every history entry are checked against the route format: unknown fields are dropped, numbers and codes must be what they claim, text is plain and capped, and files over 1 MB are refused unread. The insight saved in an export is computed again instead of trusted. Before, text from such a file could reach the window as markup: an image tag that made Windows send the user's network login hash to another machine, or a link styled as an AS number that opened a local file. - Text is text everywhere in the window. Every value from a route, an online answer or the origin lookup is escaped where it is shown, every label without markup is plain text, and the insight panel opens no links.
- Programs are started by full path only. The version line runs
gitonly in a source checkout and only from an absolute PATH folder, never from the current folder; the trace tools come from the engine, which takestracert.exefrom System32 only. - Private files are private. The config folder is 0700 and every file Route Map keeps in it (settings, history, the three caches, the DB-IP files, the site-code table) is 0600; a folder made by an earlier version is tightened at start.
- Ceilings on what is read. DB-IP downloads stop past 250 MB, a
.gzimport past 500 MB unpacked, and a download is followed only to https on db-ip.com. Trace files opened in the CLI share the 1 MB cap. - Check for Updates opens only this repository's release pages and files, shows plain text, and shows the offered file's SHA-256 with the command that checks it.
- Windows installer: an install for all users always goes into Program Files (no folder choice, and a
/DIR=is not used), and an earlier version's uninstaller runs elevated only from there. The PATH option now adds abinfolder holding only aroutemap-clilauncher, not the folder with every DLL. - Smaller ones: the suggested export file name keeps only letters, digits, dot, underscore and hyphen from the target; Copy Hop Table puts an apostrophe before a text cell that would start a spreadsheet formula;
routemap sites updatechecks every row of a new site-code table before it replaces the one in use.
Changed
- The PATH option on Windows puts
...\Route Map\binon PATH; the command in a terminal is stillroutemap-cli. Upgrading removes the old entry.
[0.2.0-beta.2] - 2026-10-05
Added
- Installers. Windows: one installer for a per-user install (no administrator rights) or a per-machine one (Program Files), with a Start menu entry, an uninstaller in Settings > Apps and an optional PATH entry for
routemap-cli.exe; installing a new version over an old one upgrades it. Linux:.deband.rpmpackages with a menu entry. Every release builds them from the same commit as the DMGs, the AppImage and the zip, and installs, checks and removes each one on clean Windows, Ubuntu, Debian and Fedora systems before anything is published. - Check for Updates offers the file for your system: the Windows installer, the DMG for your Mac's processor, or the
.deb,.rpmor AppImage on Linux, with a Download button that opens it in your browser.
Changed
- The same trace on every platform. Traces now probe with the engine's own ICMP prober on Windows, macOS and Linux: 30 hops, three probes per hop, one second per reply, and every router that answers a hop is listed. Windows
tracertshowed one router per hop and macOS and Linuxtracerouteused UDP probes that many destinations ignore, so the same target looked different on each. No administrator rights are needed. On a Linux system that does not allow unprivileged ICMP (net.ipv4.ping_group_range), traces fall back totraceroutewith UDP and Settings > Trace says why. The system tools remain as options (UDP, and TCP where you have administrator rights). - One look on every platform: the same style, palette, accent colour and font (IBM Plex Sans, bundled, SIL Open Font Licence) on Windows, macOS and Linux; only the window frame and the menu bar position differ.
- Theme: System (default), Light or Dark, in Settings > Map and View > Theme; applies to the window, the map and the exports, and is remembered.
- Nothing disappears without a reason. When RIPEstat or RIPE Atlas does not answer, the route summary says so and why (for example "RIPEstat did not answer within 20 s") instead of leaving a section out. The slow RIPEstat lookups (RIS paths, BGP updates, visibility) now wait up to 20 s and retry once. With no origin set, the RTT chart says why there is no physics floor.
- City labels at every zoom, the largest places first, so whether a map shows any no longer depends on the window size.
- **Help > About and
--versionshow the commit** the build was made from, and every release checks that all platforms were built from the same commit and render the same panels, legends, charts and table. - **Help > About and
--versionalso show the engine's commit** whenever the app is built on an engine commit rather than a published release. - Version spelling: the version reads
0.2.0-beta.2everywhere you see it (About,--version, file names, installer, Settings > Apps, packages), the same as the release tag; earlier releases' files used0.2.0b1. - Requires routemap-engine 0.4.0.
Fixed
- Windows: round trip times keep their decimals. Every probe is timed with the same high-resolution clock on every platform; on Windows, hops beyond the access network used to read as whole milliseconds.
- The built-in prober is named as such ("Built-in ICMP prober"), not "Unix traceroute", from the first line of a trace.
- Disagreeing RIS paths are explained: the BGP view says where they leave the trace's path and through which AS, also when some paths agree.
- The BGP updates chart marks the hours RIPEstat has no data for yet (hatched, with the time its data reaches) instead of drawing them as quiet.
- The Hoiho ruleset date is always shown, also when the answers came from the cache.
- One RPKI term: a prefix without a ROA is "not found" in the hop table, the PDF, the AS path and the BGP view alike (the table said "no ROA").
[0.2.0-beta.1] - 2026-10-04
Added
- Globe. Flat or globe (View > Globe, Ctrl+G, or Settings > Map). The globe is centred on the route and turns when dragged.
- Great-circle lines coloured by RTT step: grey under 15 ms, warming to the hot colour at 60 ms, both thresholds in Settings > Map. Dashed across silent hops and country-only placements. A legend says which is which.
- Replay (Ctrl+R) draws the route again hop by hop.
- Finer map when zoomed in: Natural Earth 1:10m coastlines and borders, and city labels from Natural Earth's own zoom levels.
- Route summary beside the table: AS path with RPKI badges, countries transited with your sensitive countries flagged, a likely-anycast note, a typical latency for the trip from RIPE Atlas anchors, what RIPE RIS peers see for the destination prefix (path agreement, visibility), and the last 48 hours of BGP updates for it.
- RTT sparkline against the lowest RTT each placement allows.
- Hop details: AS, routed prefix, RIR, RPKI, abuse contact with Copy, AS overview, and Open in FalconEye (IP Reputation, address on the clipboard; also on the table's right-click menu).
- ASN and RPKI columns in the hop table.
- Compare two runs: Trace Again and Compare, Compare with an Export, and Compare with an Earlier Atlas Measurement (your own, no credits). Hops are matched by place; the PDF and JSON include the comparison.
- Offline IP databases: DB-IP Lite ASN ships with the app; DB-IP Lite City is offered on first run (about 60 MB), or imported from a file on a machine with no internet, and updated from Settings or
routemap data update. While City is not installed, IP database placements come from RIPEstat and the Source column says so. IP Geolocation by DB-IP, CC BY 4.0. - One Online lookups switch (Settings > Sources): off, nothing new leaves the machine.
- Command line:
routemap data update|import|status,--compare FILE; PDF and--envelopeJSON carry the route summary.
Fixed
- Map navigation. A trackpad pinch did nothing (macOS sends it as a native gesture, which no part of the map handled); two-finger scroll crept the zoom instead of panning; and after Fit on a long route the wheel could not zoom out, because the zoom floor sat at about the fit's own scale. Now the wheel zooms around the pointer, pinch zooms around the fingers, two-finger scroll pans (turns the globe), double-click zooms in,
+,-, arrows and0work after clicking the map, and zoom stops at the whole world and at city-street level.
Changed
- An IP database placement between two hops in one area is rejected when the RTT did not rise enough for the detour (engine 0.3.0). It showed on the sample: DB-IP put heise's hop 12 in Chicago between two Frankfurt hops.
- JSON export format version 2 (adds
insight,attributionsandcomparison; version 1 files still open). Itsschemalink now points at the engine repository, where the schema lives. - PRIVACY.md and Help > Privacy list the new lookups: RIPEstat route details, RIPE Atlas anchor baselines, DB-IP downloads.
- Engine: routemap-engine 0.3.0 from PyPI.
Not in this release
- Submarine cables: TeleGeography's cable data is sold under licence (only its map images are CC BY-SA), so there is no cable overlay.
- Internet exchange points: PeeringDB's terms do not allow bundling its prefix list; permission is being asked and the code is switched off until then.
[0.1.0-beta.5] - 2026-10-04
Changed
- Help > Support Route Map lists the ways to support the project, in order: Ko-fi, PayPal, Bitcoin and Monero, with the addresses selectable and copyable. It opens only when you choose it. GitHub Sponsors is gone.
- Contact: [email protected], in Help > About and Help > Privacy.
- The bundled sample trace no longer shows the maintainer's home network: the router, LAN, carrier-NAT and first ISP hops carry documentation addresses (192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24).
- Settings: the cache line now covers both caches, Hoiho and the IP database, and counts both.
- The engine comes from PyPI (routemap-engine 0.2.1, the same code as before).
- Documentation: a fuller user guide (exports, paste mode, settings, RIPE Atlas), troubleshooting, known limitations and a FAQ. Corrected:
mtr --jsonoutput was never supported;mtr --reportis.
[0.1.0-beta.4] - 2026-10-04
Changed
- Route Map is free and open source under the GNU AGPL-3.0, and its repository is public. Contributions are welcome under a Contributor Licence Agreement (CLA.md, CONTRIBUTING.md). No licence key is needed.
- Releases are on GitHub Releases, with a GPG-signed
SHA256SUMS. - Windows: a zip instead of a single exe. Extract it and run
routemap.exein theRoute Mapfolder;routemap-cli.exeis beside it. beta.3's one-file exe, which unpacked itself at start, was deleted by Microsoft Defender on download as a false positive. Both exes now carry full version information and an application manifest, no packer is used, and every Windows build is scanned with Defender before release. The Windows build is still unsigned. - Help > Support Route Map opens the project's sponsor page (nothing else, and never on its own). Help > About links the project site.
- Help > Privacy and PRIVACY.md now spell out everything an Atlas trace sends.
[0.1.0-beta.3] - 2026-10-03
Fixed
- Hops at the end of a trace that answered but could not be placed were labelled "No reply". They are now "not placed", and the legend says "Not placed (yet)" while a trace is running.
routemap-cli.exeon Windows wrote redirected output (to a file or a pipe) in the ANSI code page, so separators and accented city names came out as replacement characters. Redirected output is now UTF-8.
Changed
- RIPEstat answers are cached on this computer for the same 30 days as Hoiho answers (
ipgeo-cache.sqlite3), so a route traced again does not ask RIPEstat again. "Clear cache" clears both. - RIPEstat requests identify the app with
sourceapp=routemap-desktop(routemap-engine 0.2.1).
[0.1.0-beta.2] - 2026-10-03
Fixes from beta 1 on real Windows 11 hardware, and a compiled build.
Changed since beta.1
- Windows: no console.
routemap.exeis now a windowed program: it never opens a console or Windows Terminal tab, and closing a terminal it was started from no longer closes the app. The command line is a separateroutemap-cli.exe. - Hops appear as the trace runs. Each hop is placed on the map and added to the table the moment its line arrives (hostname first, the usual sources, the RTT bound); hops that do not answer show at once as a dashed "no reply" marker. When the tool finishes, only ECMP cleanup and the annotations are added. The map keeps fitting the hops so far until you zoom or pan; Fit hands it back.
- Nothing covers the map while tracing. The tracing card is gone; state is in the status bar, with a small indicator next to Stop.
- Right panel. The hop table is on top and grows live; the tool's raw output is in a collapsible panel below it, collapsed by default (View > Tool Output).
- Selection follows both ways. Click a marker to select its rows (all of them for a collapsed marker such as "14-15"); click a row, or move with the arrow keys, to highlight and centre its marker. Esc clears.
- Country-only placements are marked. A hop the IP database could place only to a country (for example
apa.customers.nextlayer.net, "AT") is drawn as a hollow marker labelled "AT (country only)", shows "ip-db, country only" in the Source column, and no longer stretches Fit. - Marker hover shows the same fields as the table row: hop, location, hostname, IP, RTT, loss, source and notes.
- Compiled build. The app is compiled with Nuitka on every platform.
- Help > Third-Party Notices lists every bundled component with its licence.
- Beta builds were handed to testers through a download site with a login for each tester, with a GPG-signed
SHA256SUMS.
[0.1.0-beta.1] - 2026-10-03
The first desktop build, for trying on real machines. Not code-signed yet.
Added
- The desktop app on macOS (Apple silicon and Intel), Windows and Linux: trace from this machine with the system's own tracert, traceroute or mtr, with the tool's output streaming into the window, then the route on an offline world map and in a sortable, copyable hop table, with unplaced hops and their reasons.
- Paste or open a trace run elsewhere; open a JSON export again.
- Exports: a 1600 x 900 PNG of the whole route with legend and provenance; a PDF report with the facts of the trace, the map, the hop table, unplaced hops, how locations were decided and the raw trace as an appendix; the JSON route model with the trace text, tool and flags.
- Origin from the public IP (city level, labelled approximate), or set in Settings by city search (offline), coordinates or a click on the map.
- Settings for the trace tool and flags (probe types that need administrator rights are flagged, never escalated), each network source, the Hoiho cache lifetime, RIPE Atlas and history. Everything is kept in one config folder.
- Optional RIPE Atlas traces with your own key, after a one-time acknowledgement that Atlas measurements are public.
- History of the last 50 traces, off by a setting.
- The command line:
routemap TARGETwith--json,--png,--pdfand--origin;routemap parse,routemap sites update,routemap cache clear,routemap --check-update. - Builds: a .dmg per Mac architecture (ad-hoc signed so it runs on Apple silicon), a Windows .exe, a Linux AppImage and .tar.gz, each smoke-tested in CI by opening the window offscreen, loading a trace and exporting all three formats.
Earlier, toward this beta
- The Route Map engine, extracted from FalconEye v3.35.3 into
routemap.engine: the tracert, traceroute and mtr parsers, PTR resolution, the CAIDA Hoiho client, the carrier site-code table and its generator, the bundled GeoNames city list, the RIPEstat IP geolocation fallback, the RTT physics bound, the hop annotations and ECMP handling. Behaviour is unchanged; FalconEye v3.36.0 runs its Route Map tab on this package. analyse(trace_text | hops, origin) -> Route, with every network source passed in as aSourcesvalue rather than read from configuration, a per-source progress callback, andgeo.OFFLINEfor a run that contacts nothing.Route.to_dict()and its JSON Schema,routemap/engine/route.schema.json.run_trace(target, options): runs the system tracert, traceroute or mtr with an argument list (never a shell), streams output line by line, and supports cancel and a timeout.- Pluggable Hoiho answer caches: none, in memory, or one SQLite file.
routemap parse FILEon the command line.- The desktop window, as a static mockup for review: the offline Natural Earth 1:50m world map (public domain, about 114 KB bundled), route markers that collapse same-city hops, unwrap across the antimeridian and move aside with a leader line when they would overlap, the sortable hop table, unplaced hops with reasons, live trace output, history, settings, export, paste and RIPE Atlas dialogs, light and dark.
python -m routemap.gui.mockuprenders every state from real recorded traces.
Tagged
v0.1.0.dev1(2026-10-03): the engine extraction FalconEye v3.36.0 pins.