Hello friends, since 2 days I have make a new traceroute and I found 3ms less! But I have chase this 3ms since one month across 4 providers lol. I will explain my journey because maybe it can help someone. I play on the game server of my friend in Tokyo, I am in Lyon. First provider: RackNerd, 247ms. Second: HostHatch, 244ms. Third: GreenCloudVPS, 242ms. Fourth: CloudCone, 239ms. Each time I change, I document everything in the spreadsheet. The route via Palo Alto was bad, now I go via Seattle then direct to Tokyo. It is possible to do that? Yes because I ask nicely to the NOC But I want 236ms, it is my goal. The game is StarVoid, very competitive, the 3ms it is the difference for the ranking.
Latency hunt: I chased 3ms across 4 providers for a month
Vive la résistance... électrique
Actually this is very impressive work with the tracerouteOptimization and the providerSwitching but I must ask why the gameServerLatency is so important for you because normally the humanReactionTime is much slower than 3ms or? The networkEngineering aspect is solid though I respect the documentationHabit.
Which kernel and OS were you running for the traceroutes?
swimming upstream since 2019 🐟
I dont think 3ms matters for gaming honestly
Ned never played StarVoid at 239ms against a Tokyo lobby