If 203.0.113.45 is real in production, that's a ripe for abuse report. TEST-NET should not route. Somebody fat-fingered an ACL or the whole path is a GRE tunnel with weird encapsulation.
I have seen worse. Carrier I won't name used 192.0.2.0/24 for internal loopbacks once. Took them two years to fix.
Member
I host for people at parties. They ask "why my website slow" and I say "submarine cable" and they think I make it up.
Now I have KnownHost status page to show them. Thank you thread.
Following. I have Hetzner VPS in Helsinki, no Asia path issues, but this thread taught me about TEST-NET leakage. Subscribed.
This. I came for traceroute help, stayed for the IP space archaeology.
Could be your ISP's CGNAT logging leaking into traceroute display. Some Indonesian providers rewrite hop responses for "security." I don't trust anything after hop 3 in ASEAN networks.
Run tcptraceroute to port 80, compare path. TCP and ICMP often diverge.
Same here. Contabo user in EU, no 150ms spike to my Nuremberg VPS. This is Asia routing specific. MeritBudi try traceroute from your OVHcloud Gravelines to Contabo Singapore, see if path symmetric.
