Loading
This measures the round-trip from the connection you are on right now to nine cities, then puts it next to the same measurement taken from the Fire-IT backbone in Johannesburg. It takes about half a minute.
Both columns are an HTTPS round-trip to the same endpoint in each city, measured the same way, so the difference is your route and ours rather than two different tests.
No browser-reachable endpoint exists in these cities, so we publish our own ICMP figure and leave the comparison column empty rather than guess: Moscow 201 ms, Miami 229 ms.
Latency is a timed HTTPS request to a regional endpoint in each city. The first request to each is thrown away because it pays for DNS, TCP and TLS setup; the figure shown is the median of the five that follow on the same connection. Measured that way, it lands within a few milliseconds of a real ICMP ping to the same region.
The Fire-IT column is the identical request, to the identical endpoint, run from our Johannesburg network. Two cities, Miami and Moscow, have no endpoint a browser is allowed to reach, so those are reported as our own ICMP readings and left out of the comparison rather than measured a different way and presented as equivalent.
Download and upload run against Cloudflare rather than our own servers, so the number is not one we can flatter. The separate “to Fire-IT” figure is the leg that matters if you host with us, and that one is ours.
Results are recorded so we can build a picture of how different South African networks perform. A result only appears on this page as a named comparison if we choose to publish it, and never with anything that identifies who ran it.
If your line is the bottleneck, we can quote fibre, LTE failover or a move onto our network. Send us the result and we will read it with you.