220
Measuring the latency of 574k servers around the world from my lemmy server (files.catbox.moe)
submitted 1 year ago* (last edited 1 year ago) by to c/map_enthusiasts@sopuli.xyz
32 comments fedilink hide all child comments
 

Located in London, I measured the RTT or round trip time to 574,691 random webservers and plotted the times on the globe.

Discovery was done with masscan, measurements using hping and plotting with an old Python script I've revived and enhanced.

This is part of the next writeup on my blog, with which I will be posting any of the code I've used.

Full write-up and code

Blog / How I made a blog using Lemmy

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (1 child)

I haven’t digested this whole paper, but it seems like it would be faster than fiber all the way. https://people.eecs.berkeley.edu/~sylvia/cs268-2019/papers/starlink.pdf

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 1 year ago* (last edited 1 year ago)

    Thanks for the source :)

    Starlink’s LEO satellites will be in 1,110 to 1,325 km orbits. Although much lower than GEO, this is still too high to pro- vide lower latency than fiber over shorter distances. However, over longer distances the extra latency getting between Earth and the nearest satellite may be more than offset by routing around the world between the satellites at c.

    So yeah makes sense. The inital distance to space completely tanks the short distance latency, but eventually gets compensated by the higher transmissions speed when trying to cover longer distances. I havent found it yet, but what i really wanna know is the distance value at which sat overtakes fiber. I dont think this paper covers that sadly.

  • permalink
  • fedilink
  • source
  • parent