Finally did it. 10 VPS across 10 countries, all linked with WireGuard mesh. Traceroute map attached—literally just wanted to see the lines on a map.
racknerd.com → racknerd.com → hosthatch.com → ...No containers involved, actually docker is just unnecessary complexity for this. Systemd-networkd handles the tunnels. Þetta reddast.
Why? No reason. Looks cool. That's the whole post.
Back in my day you had to phone a BBS in the next county and pray the 2400 baud didn't drop :-) now you spin up a box in uzbekistan for pocket change. R the latencies actually usable or just for the map
1. Practical uses you are missing:
1. A) geo-dns testing
1. B) anycast learning lab
1. C) latency baseline collection
2. Questions about your setup:
2. I) what routing daemon
2. Ii) manual wireguard (https://www.wireguard.com) or automated
3. Personal opinion:
3. This is actually cool
3. A) no sarcasm
3. B) would like config files
Ten nodes full mesh yields 45 tunnels. Manual key management scales poorly; consider deploying RPKI-validated BGP sessions to each instead, using private ASN. You'd gain dynamic routing, community-based traffic engineering, and proper path visibility.
Transit pricing varies dramatically by region—your Singapore-Ams route likely costs your provider 3-4x the London-Frankfurt leg. The map hides economic topology.
Member
The latency it is not good XD
The map it is good XD
Ten server, will use for... nothing? Respect. Will do same. Maybe.
$ ping -c 1 hosthatch.com
rtt min/avg/max = 312/315/318 msThe 312ms it is ART. Will frame.