this post was submitted on 19 May 2025
1 points (100.0% liked)

Map Enthusiasts

4669 readers
10 users here now

For the map enthused!

Rules:

founded 2 years ago
MODERATORS
 

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
[–] [email protected] 0 points 1 month ago* (last edited 1 month ago) (1 children)

Could you calculate shortest distance to each point (using for example haversine formula) and then divide each time you got by 2*distance/c to get some sort of normalized score for connectivity? Anything closely approaching 1 would be the optimal connectivity to that destination.

Edit: c would be speed of light

[–] [email protected] 0 points 1 month ago (1 children)

In normal fiber optic cables the signal only travels at ~60% of speed of light. I dont think hollow core fibers are widely adopted yet for undersea cables, so the results should reflect that. Ofcourse you also have delays due to the relay stations in between, but those are probably quite small.

[–] [email protected] 0 points 1 month ago (1 children)

LEO satellite comms coming online to route some of this traffic should be closer to c since will relay satellite to satellite to the last mile ground station to then reach the destination.

[–] [email protected] 1 points 1 month ago

It is faster per distance covered, but the distance that needs to be covered is significantly larger so it cancels out i think.