Tuning the measurement to 5 minutes each, the result portal summarizes the data in a single file by RIPE Atlas Probe ID.
The results show a predictable pattern of latency changes with increases and decreases, which may indicate satellite movement. We assume that the latency between the ground station, CDN server, and client site remains constant (unless under a DDoS attack… um…).
With the current resources available on RIPE Atlas, can we compare country-based latency and service levels of Starlink? Ah, that should probably be done by the Starlink NOC…
Referencing some studies on Starlink and SpaceX, this is a great example of low-Earth orbit (LEO) satellite technology providing high-bandwidth network access. However, as you know, no matter how large the bandwidth, latency remains one of the key factors affecting user experience and application traffic performance.
Moreover, satellites are linked to ground stations, which then connect to Internet peering or exchange points to retrieve the required data via traffic routing. This total latency may not always be predictable due to satellite movement, variations in the distance between the user’s access antenna and the satellite, and the routing path between the ground station and the client machine.
Now, imagine if a CDN node were in space—embedded within the satellite itself. If a satellite operated as a Layer 3 router gateway, could we integrate a server farm with SSD storage to provide caching and content delivery services?
