city:tokyo
7 endpoints across 6 services.
How It Works
1
Your browser pings the service
Real latency from your network
2
Our servers check too
Probes from multiple global regions
3
Compare with the community
Crowdsourced data from other users
What you'll see
✓ Connected to 5/5 · Median 34ms · Slowest: Example CDN at 89ms
Example API
https://api.example.com
✓ HTTP 200 42ms
Server: 38ms (4ms faster) | Community: 45ms (3ms slower)
Your latency front and center, with server and community comparisons below each endpoint. Learn more in the FAQ
Checking 7 endpoints…
Sort:
EC2 Tokyo
https://ec2.ap-northeast-1.amazonaws.com
Waiting
S3 Tokyo
https://s3.ap-northeast-1.amazonaws.com
Waiting
Cognitive Services Japan East
https://japaneast.api.cognitive.microsoft.com
Waiting
Cloud Run Tokyo
https://asia-northeast1-run.googleapis.com
Waiting
Linode Tokyo
https://speedtest.tokyo2.linode.com
Waiting
OCI Storage Tokyo
https://objectstorage.ap-tokyo-1.oraclecloud.com
Waiting
Vultr Tokyo
https://hnd-jp-ping.vultr.com
Waiting