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…
Using the Atlas RIPE probe (what a great network measurement platform!), we selected the probe, which uses Starlink to continuously measure connections to CDN servers.
We assume that, no matter which Starlink satellites are passing over the area, the network service connection will still be provided to the same region. For example, if the satellites are crossing the US regions, it doesn’t matter which satellite; it will send data back to a US-based station on the ground.
The test seems a bit funny, but the latency trend appears to follow a pattern. It shows a progression from high latency to low latency and then back to high latency over time. Assuming that the ground station link is a fixed connection to destination CDN server, the latency remains constant. Therefore, the movement of the satellites affects the latency. When the latency decreases, it suggests that another satellite has taken over that area, and the roaming process is complete.
You can think of this like when you are using a mobile device. As you move from one cell site (A) to another (B), roaming occurs, which registers your device from Cell Site A to Cell Site B. This is a similar process with satellites.
Now, back to the Starlink client probe: if its location doesn’t change, then as the satellites move through space, the distance between the satellites and the probe site will increase, and latency can indicate this. When the latency decreases, we may assume that another satellite has taken over the service coverage (similar to the roaming process). This is because the satellites do not move backward.
Moreover, does the change in latency over time affect the user experience? For instance, during a video or voice call, latency may fluctuate—increasing or decreasing.
However, live gameplay presents a different scenario. Unlike calls, it often relies on a stable connection. A fixed connection typically doesn’t exhibit the same fluctuating physical characteristics, making latency more predictable in gaming environments.
Currently, measurements are taken every 15 minutes. If we shorten this test period, we may get more accurate insights into this operation.
As a Wide Area Network (WAN), the circuit provided by telecom backhaul between two endpoints—whether it’s point-to-point between two sites (EVPL, SDH) or customer site to provider PE (Internet, IPVPN, VPLS, etc.)—should be connected to the provider’s equipment or router devices to deliver the service. If you’re referring to dark fiber in a limited area… um… okay, next.
How do you verify the circuit service? Check your site router configuration? Check your IP routing?
The basic mindset: I believe we should start by checking the cabling. Yes, Layer 1, isn’t it?
If your port is UP and able to send and receive packets, WELL, at least confirm both endpoint IP addresses and perform a ping test. (Yes, a PING test—please don’t tell me you don’t know what PING is.)
PIC from #Google
From past experience, field engineers often argue that the device configuration is incorrect, but guess what? The issue ends up being the WRONG port connected.
Therefore, HOW IMPORTANT IS PHOTO CAPTURE!!!!!!!
What if the ping fails? Yes, it happens—cable quality issues, loose connectors, poor signaling, etc.
Have you ever checked the DUPLEX setting????????????? Confirm both ends have the SAME duplex setting!!
PIC from Cisco Press
Then you’ll mention bandwidth: “Speedtest.com, huh? Why can’t I get full bandwidth?!”
Please understand: we cannot guarantee a test server will allocate all resources for your test. The Internet is unmanaged, and you need to be aware of overhead and your device’s processing power. Do you really think your mobile can hit 2Gbps over Wi-Fi, bro?
For standard testing, running tests between the client site and the ISP backhaul provides a great reference for your service quality—this is typically done during installation.
But anyway… PLEASE confirm the cabling is correct before spending too much time checking the configuration. Start with Layer 1 first!
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?
If you are thinking of how to enhance your Internet performance, it is great that you can subscribe a higher bandwidth Internet service. But is it the right way?
No really.
Increasing the bandwidth cannot shortern the latency between you and the destination server. But You cannot control our provider’s network path.
Under the current Web server depolyment, using the Content Delivery Network to deliver the content to Internet is a comment way. However, your network provider’s DNS server may not response the optimial server for the request domain. Therefore, you cannot enjoy the lowest latency between you and the request server.
HOW to?
A little measurement you can do, you can try to make a query to several publilc DNS servers, the reponse result may not be the same. For Example, by 8.8.8.8 Google or 1.1.1.1 Cloudflare. Based on the result, a simple ping test you can perform and record the lower latency one. Finally, you can setup a bind server to forware the domain to that DNS server to have a better Internet performance.
Using RIPE Atlas to perform the global network latency map. Atlas Probes are existing world wide and let you to perform the measurement by using your CREDIT. Self developed Python automation program used to perform the test by RIPE Atlas API.
