Tokyo (Lightsail)
ap-northeast-1- Provider
- AWS Lightsail
- ASN
- AS16509 — Amazon
- 30-day uptime
- 99.94%
- Bandwidth (mo.)
- 4123 GB / 5000 GB
Tool · Probe Network · Live
Reachability, measured.
Round-trip times, TLS handshake durations, and reachability from the RouteHarden test fleet to common production destinations. The fleet spans four egress points across Asia, Europe, and the UK. Refreshed on a every 30 min cadence.
Probe fleet
Tokyo (DMIT)
ap-northeast-1- Provider
- DMIT
- ASN
- AS6939 — HE / DMIT
- 30-day uptime
- 99.86%
- Bandwidth (mo.)
- 612 GB / 2000 GB
Frankfurt (Lightsail)
eu-central-1- Provider
- AWS Lightsail
- ASN
- AS16509 — Amazon
- 30-day uptime
- 99.99%
- Bandwidth (mo.)
- 1844 GB / 5000 GB
London (relay)
eu-west-2- Provider
- Self-hosted
- ASN
- AS8190 — Andrews & Arnold
- 30-day uptime
- 99.98%
- Bandwidth (mo.)
- 230 GB
Reachability matrix · RTT p50 (ms)
| Destination | Purpose | Tokyo | Tokyo | Frankfurt | London |
|---|---|---|---|---|---|
| github.com | Source control / CI | 132 · p95 168 | 118 · p95 154 | 85 · p95 112 | 78 · p95 96 |
| registry.npmjs.org | Node package fetches | 4 · p95 9 | 6 · p95 14 | 3 · p95 7 | 11 · p95 24 |
| 1.1.1.1 | Cloudflare DNS reachability | 2 · p95 6 | 3 · p95 8 | 1 · p95 4 | 2 · p95 5 |
| api.stripe.com | Payment processor | 92 · p95 118 | 88 · p95 114 | 12 · p95 24 | 9 · p95 18 |
| deb.debian.org | Apt metadata refresh | 88 · p95 142 | 82 · p95 122 | 6 · p95 14 | 14 · p95 28 |
| cloudflare.com | Cloudflare control plane | 3 · p95 8 | 4 · p95 10 | 2 · p95 6 | 3 · p95 7 |
Cells show RTT p50 in milliseconds; tooltip exposes p95 and notes. Color tiers: under 30 ms (ok), 30–90 (mid), 90–180 (warn), over 180 (bad).
TLS handshake p50 (ms)
| Destination | Tokyo | Tokyo | Frankfurt | London |
|---|---|---|---|---|
| github.com | 248 | 226 | 178 | 158 |
| registry.npmjs.org | 18 | 22 | 15 | 30 |
| 1.1.1.1 | — | — | — | — |
| api.stripe.com | 184 | 178 | 42 | 36 |
| deb.debian.org | 198 | 188 | 28 | 42 |
| cloudflare.com | — | — | — | — |
What you're looking at
The probe fleet is a small set of egress nodes RouteHarden runs across providers and continents. Each probe runs the same harness: HTTPS to the destination, measure connect/TLS/round-trip, log it. Numbers are medians and p95s over the last refresh window.
Use this when picking which provider to put workloads on next to which destinations. Sometimes the obvious answer (“same region!”) is wrong because of peering. DMIT vs Lightsail in Tokyo and Evaluating VPS providers cover the methodology.
Hire the fleet
Want this kind of probing for your stack?
RouteHarden builds reachability dashboards as part of the hardening engagement — your real destinations, your real egress points, your on-call channel when something breaks.