Looking glass function provided by RIPE Atlas?

I performed some traceroute tests using the public looking glass of another organization/provider. I found that some test functions, like Ping and Traceroute, were launched using RIPE Atlas probes. It looks impressive and kind of funny.

In the previous year, the provider developed a web interface and API to launch commands from their own PE (Provider Edge) or Internet BG (Border Gateway) routers and return the results. The geographical router list allows users to select region-based tests.

This seems to be a new method using RIPE Atlas, where queries can be made via an API. The web interface lets users select which probe to use for the measurement, deducting the web provider’s “RIPE Atlas Credits” for each test.

However, I’m wondering — since looking glass aims to provide insights into a specific network provider’s or AS owner’s network — if we’re using this method, why not just go to the official RIPE Atlas website to launch the test?

Well, I guess the more user-friendly web portal makes it easier for users.

Pingnetbox – http://www.pingnetbox.com

#ripe #atlas #lookingglass #measurement #ping #traceroute #test #internet #AS #chatgpt #proofreading

Starlink Satellites’ Movement Proven by Periodical Measurement – Part 2

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…

https://www.bgptrace.com/atlas/starlink

#starlink #CDN #cloudflare #satellites #ping #latency #movement #probe #RIPE #atlas

The latency between satellites and CDN. What if CDN at Space?

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?

#ripe #atlas #starlink #cloudflare #CDN #latency

https://bgptrace.com/atlas/starlink

[1] Poster: Twinkle, Twinkle, Streaming Star: Illuminating CDN Performance over Starlink, Nitinder Mohan – Delft University of Technology – Delft, Netherlands, Rohan Bose – Technical University of Munich – Munich, Germany, Jörg Ott – Technical University of Munich – Munich, Germany, IMC ’24, November 4–6, 2024, Madrid, Spain https://www.nitindermohan.com/documents/2024/pubs/leoCDN_IMC2024_poster.pdf

Global Latency Map – by using RIPE Atlas

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.

Access the following to see our work.

https://www.bgptrace.com/atlas/ping_map.html

Can Starlink to be a testable probe?

More Information: https://atlas.ripe.net/

#ripe #Internet #measurement #python #automation #latency #starlink #atlas