Measure the path your packets actually take.
Northmesh runs continuous RTT, loss and path-stability probes from 214 metros into 4,100+ networks, so you can see how routing changes change your users' experience — before they open a ticket.
Where we measure from
Vantage points sit inside carrier-neutral facilities and run on dedicated probes with GPS-disciplined clocks. Every sample is tagged with the observed AS path.
| Metro | Region | Networks | p50 RTT | p95 RTT | Loss | 24h |
|---|---|---|---|---|---|---|
| FRAFrankfurt | Europe | 1,284 | 7.9 ms | 18.4 ms | 0.003% | nominal |
| AMSAmsterdam | Europe | 1,190 | 8.4 ms | 19.7 ms | 0.002% | nominal |
| LHRLondon | Europe | 1,112 | 9.1 ms | 21.3 ms | 0.004% | nominal |
| CDGParis | Europe | 1,038 | 9.6 ms | 22.9 ms | 0.003% | nominal |
| IADAshburn | North America | 1,356 | 11.3 ms | 26.1 ms | 0.005% | nominal |
| SFOSan Francisco | North America | 1,021 | 12.8 ms | 29.4 ms | 0.006% | nominal |
| SINSingapore | Asia-Pacific | 986 | 15.4 ms | 34.8 ms | 0.008% | nominal |
| NRTTokyo | Asia-Pacific | 942 | 18.2 ms | 41.6 ms | 0.011% | degraded |
| SYDSydney | Asia-Pacific | 764 | 21.7 ms | 48.2 ms | 0.009% | nominal |
| GRUSão Paulo | South America | 688 | 26.4 ms | 57.9 ms | 0.014% | nominal |
One endpoint. Every prefix.
Query historical and live RTT for any announced prefix or ASN. Responses include the witness count, sample volume and observed path — so a median is never just a number you have to trust.
GET /v3/rttLive and 90-day RTT percentilesGET /v3/prefixes/:cidrAnnouncement history, RPKI stateGET /v3/pathsObserved AS paths between witnessesGET /v3/incidentsRouting and reachability eventsBearer token auth · 600 req/min on Team · JSON and Protobuf · OpenAPI 3.1
$ curl -s https://api.northmesh.net/v3/rtt \
-H "Authorization: Bearer $NM_TOKEN" \
-d prefix=2001:db8::/32
{
"prefix": "2001:db8::/32",
"origin_asn": 64512,
"window": "2026-11-20T13:00Z/PT1H",
"samples": 48213,
"witnesses": 214,
"rtt": {
"p50_ms": 12.4,
"p95_ms": 31.8,
"p99_ms": 58.2,
"jitter_ms": 2.1
},
"loss_pct": 0.004,
"path_stability": 0.997,
"observed_as_paths": [
"210483 1299 64512",
"210483 3356 64512"
]
}
All systems operational
Live availability of ingestion, measurement and public endpoints. 90 days of history, updated every 30 seconds.
Jul 1 – Nov 20, 2026 · RSS · Incident history
Transit path shift on upstream AS1299; traffic re-anycast to AMS-2 within 41 s. Resolved after 38 min.
Query queue saturation during a bulk import. No failed requests. Resolved after 12 min.
Rolling deployment across 214 probes. No customer-visible impact.
Start free, scale by measurement volume
Pricing is per API request and probe-hour, not per seat. Every plan includes the full vantage set and raw AS-path data.
Developer
- 10,000 requests / month
- 24-hour retention
- All 214 metros
- Community support
Team
- 5M requests / month included
- 13-month retention
- Alerting, webhooks, SSO
- Prefix and ASN budgets
- Email support, 4h SLA
Enterprise
- Dedicated vantage points
- BGP feed and IRR integration
- 99.99% availability SLA
- Security review & DPA
Built for network engineers
Guides for measurement design, baseline selection, RPKI-aware routing checks and alert routing. Every example is runnable against the public sandbox.
quickstartYour first prefix query in 3 minutesconcepts/baselinesTime-of-day RTT baselines and peer groupsconcepts/path-stabilityDetecting transit changes without alertsguides/alertingRouting alerts into PagerDuty and Opsgeniereference/openapiFull OpenAPI 3.1 schema