Manchester. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Vultr |
|---|---|
| Region code | man-uk |
| Region name | Manchester |
| Datacentre city | Manchester, GB |
| Coordinates | 53.48, -2.24 |
| Published IPv4 prefixes | 2 |
| Probe endpoint | https://man-uk-ping.vultr.com/vultr.com.100MB.bin |
| Probe style | a CORS request whose reply the page can read |
| 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 Manchester 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 | 5,370 km | 54 ms |
| Los Angeles | 8,504 km | 85 ms |
| São Paulo | 9,569 km | 96 ms |
| London | 262 km | 2.6 ms |
| Frankfurt | 838 km | 8.4 ms |
| Johannesburg | 9,329 km | 93 ms |
| Dubai | 5,654 km | 57 ms |
| Mumbai | 7,336 km | 73 ms |
| Singapore | 10,939 km | 109 ms |
| Tokyo | 9,444 km | 94 ms |
| Sydney | 16,997 km | 170 ms |
The closest regions to Manchester on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to man-uk depends on your connection and the route it takes — open the instrument, pick Vultr, 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 Vultr region on the Vultr latency page.