If the target server is far away and the signal goes 7000 km from satellite to satellite in space before coming back down, then your signal it will need at least 46.7ms more in space for a 14km round trip in space, which results in a minimum possible ping of 60ms to ping a server 7000 km away. Fiber-optics are 30% slower than radio links, so this 60ms minimum is 10% lower latency than the best fiber-optics can do: (7000 km / .7 speed-of-light) = 66ms
If the distance to your server is 2.333x the distance to your satellite you will have lower latency with radio than fiber optics. Bringing the altitude of the satellites down will make a big difference, but you also need a lot more of them in a constellation to have low average distances.
I thought that the US servers for most games are in the middle of the country to get the best average ping for a cross-country audience. Blizzard is like Chicago and Texas.
The majority of the population in the US is in the eastern half (1/3 in states on the East coast), so you don't actually decrease median latency by putting datacenters in the geographic center: https://commons.wikimedia.org/wiki/File:United_States_popula...
https://en.wikipedia.org/wiki/Mean_center_of_the_United_Stat...
Actually not too far away from the geographic center which is somewhere in Kansas.
Assuming terrestrial lines travel as the crow flies, which is not all that likely (but probably not too far off).
> At 200 miles up where they intend to put the satellites orbiting over major cities, it's going to be about 1000 mile round trip.
Other people here are noting that fiber signals travel at ~70% the speed of light, while radio waves travel at very close to the speed of light. If that's true, it puts the optimal time for land based optical communication at ~3.3ms[1] ms, while the optimal time for a low orbit satellite at ~5.4ms[2] (if I didn't screw up the math). That's slower, but not by a whole lot, so it might even be better than you're predicting.
Also, are people actually getting sub 4ms round trip times between Boston and New York? If not, then the difference here might be entirely subsumed by other factors.
1: 430 Miles / 186,000 M/s / 0.70 = 0.0033 s
2: 1000 Miles / 186,000 Miles/s = 0.0054 s
The difference in latency won't be nearly as bad as a naive comparison of these two numbers would suggest. Depending on what hops your terrestrial traffic is going through, the satellite transmission could well be faster. To give you a trivial example, I'm seeing 11 ms ping right now to a server within my own city, that's only a couple miles away. This is ~0% signal transmission delay and ~100% switching delay.
But I don't see why it's relevant. Forwarding in modern ISP routers is on the tens to hundreds of microseconds level, even if there are many hops it does not add up to that much. So what he has is likely not "switching delay", and even saying that 11ms is 100% switching delay when it's the same city (low amount of hops even if multiple ISP's are involved) is just ridiculous.
Took that number (it was for one way trip though) from memory, might be scrambled. Just checked, RTT 17ms with 3ms jitter for me.
22ms RTT is still too much though. Even with centralized network for cross-border traffic like in my country, there are IXs way closer than those 1500km to any town on european part and obviously to the East of Urals (the longest distance between IXPs is ~3000km for Krasnoyarsk-Khabarovsk, the longest distance to the closest IXP of 1500km have Norilsk - the most northern city on the globe and it's satellite Dudinka).
edit: fixed some english.
I don't think Elon is counting on gaming to be the backbone of this service.
edit - yeah I forgot about the endpoint then to the game servers data center
Maybe from me to a geographic location 400 miles away, yes. But what about 4k miles away, like coast to coast?
That would probably depend on how many satellites it has to bounce through and how far it has to travel terrestrial, but I would think there is a geographic distance where that 30ms is faster.