ana_mad
Member
- Joined:
- Jun 2024
- Posts:
- 298
- From:
- Madrid, ES
HostHatch Tokyo or HostHatch Chicago?
HostHatch Chicago. I have a storage VPS there that I use for offsite backups. Set up a wireguard tunnel (I used
https://www.wireguard.com) and routed critical traffic through it. Latency to Chicago is 95ms from Madrid, not great, but better than 180ms to St. Louis via Tokyo.
The tunnel endpoints are both in Europe so the path stays on this side.
swimming upstream since 2019 🐟
kenji3
Member
- Joined:
- Jul 2024
- Posts:
- 138
- From:
- Osaka, JP
HDD plans are in the same datacenter though, so routing would be identical.
Confirmed again. My RackNerd Dallas VPS shows normal domestic routing from Los Angeles. 35ms direct. The reverse path from North America to Dallas is where the anomaly lives.
I also tested Vultr Osaka to Dallas: 110ms, normal trans-pacific path. No loop.
conbini > datacenter snacks
lookuppierre
Member
- Joined:
- Aug 2024
- Posts:
- 113
- From:
- Lyon, France
I see nothing unusual from Lyon to Contabo St. Louis. 45ms, path via Düsseldorf then London then New York then Chicago then St. Louis. No Tokyo.
This suggests the problem is specific to trans-Atlantic routes that normally land on the US west coast. My traffic enters via the east coast.
prix fixe infrastructure: €5/mo
PetraSuper
Member
network boot believer
- Joined:
- Jun 2024
- Posts:
- 127
- From:
- Bratislava, Slovakia
45ms, path via Düsseldorf then London then New York then Chicago then St.
Same here from Bratislava. East coast entry, no jp hops. My smokeping to Contabo St. Louis is flat at 38ms.
The Seattle origin paths are the ones getting hijacked to Tokyo. Someone on the west coast is accepting a bad route announcement.
boot anything, anywhere, anytime