Chicago 1 · Chicago, US. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Akamai Cloud (Linode) |
|---|---|
| Region code | us-ord-1 |
| Region name | Chicago 1 |
| Datacentre city | Chicago, US |
| Coordinates | 41.88, -87.63 |
| Published IPv4 prefixes | 257 |
| Probe endpoint | https://us-ord-1.linodeobjects.com/ |
| Probe style | timed blind — the endpoint sends no CORS headers |
| Verification | Resolved to an address inside this region’s own published range, TCP 443 open. Checked 2026-08-21. |
Coordinates are the real datacentre city rather than the marketing region name, because they feed the distance maths below.
Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Chicago and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.
| From | Distance | Floor |
|---|---|---|
| New York | 1,144 km | 11 ms |
| Los Angeles | 2,804 km | 28 ms |
| São Paulo | 8,408 km | 84 ms |
| London | 6,353 km | 64 ms |
| Frankfurt | 6,964 km | 70 ms |
| Johannesburg | 13,983 km | 140 ms |
| Dubai | 11,638 km | 116 ms |
| Mumbai | 12,947 km | 129 ms |
| Singapore | 15,072 km | 151 ms |
| Tokyo | 10,141 km | 101 ms |
| Sydney | 14,876 km | 149 ms |
Within 75 km of Chicago — near enough that distance sets no meaningful floor between them. When several sit in one city, the fastest is the city’s real floor; a slower neighbour is usually the endpoint’s own server time.
These figures are geometry. Your own round trip to us-ord-1 depends on your connection and the route it takes — open the instrument, pick Linode, and sweep. Every region is timed from your browser against the endpoint listed above, and the result is split into the part physics demands and the part the network added.
See every Linode region on the Linode latency page.