3 ms·
It works well for people who 1. Have fiber. 2. Live in a major city that has a direct line to their datacenter. You can literally get 1-2ms latency from your
by digitallyfree 4y ago
It works well for people who
1. Have fiber.
2. Live in a major city that has a direct line to their datacenter.
You can literally get 1-2ms latency from your home to AWS/GCP/Azure with such a setup, as it's all fiber from your home->ISP->IX->datacenter and there's no additional inter-city routing. This is compared to DSL/Cable which pretty much has a ~10ms delay to the exchange in perfect conditons, and the even larger delays involved in routing a packet over multiple hops across the country.
- NSMutableSet 4y agoWould you happen to know how I can easily figure out which cities would satisfy those 2 conditions? Hopefully there's a list somewhere instead of having to manually check.
- digitallyfree 4y agoFor the first condition, that depends if you're able to get residental fiber service there. Most cities have fiber service in the downtown core but that's not always true in the suburbs. For the second condition I think that those cloud gaming services publish their available server locations or provide some sort of speed/ping test service to test your connection. Being so dependent on latency it would make sense for them to have this available to their potential customers. You can also check for IX peering info and the like but there's no guarantee that having a presence there means your game server is located there (e.g. Google may have a datacenter in the city and peer with your ISP but the Stadia servers may be somewhere else).