Somehow pings to my VPS in SG (Vultr) is significantly worse over ipv6 compared to ipv4. Anyone know whats up with that?
From 13ms to 206ms. I feel like something is off with their routing. Like, is it being routed out to US or something before being bounced back to SG?

IPv6


IPv4


This post has been edited by ruifung: Nov 21 2023, 03:17 PM

How'd you even get speedtest to work on IPv6 specifically?

For now I'm getting around their ipv6 wonkiness by routing my ipv6 traffic out through a VPS.
I got a vultr (SG) vps set up for ipv6 tunneling because the backup 4G stick don't do IPv6...


This post has been edited by ruifung: Nov 22 2023, 05:40 PM

Somehow it's routing though NTT Japan, NTT America, "Tinet GmbH", before going back to vultr in singapore. It's really going on a trip around the world....
Tracing route to 2001:19f0:4400:4001:5400:ff:fe32:b7e5 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms <REDACTED>
2 * * 7 ms 2001:d08:b1:2::2
3 * * * Request timed out.
4 14 ms 14 ms 12 ms 2001:d08:b1:22::6
5 6 ms 7 ms 7 ms 2001:218:e000:5000::3f9
6 27 ms 19 ms 7 ms ae-5.r23.kslrml02.my.bb.gin.ntt.net [2001:218:0:2000::1b2] <------------- NTT Japan
7 * * * Request timed out.
8 90 ms * 93 ms ae-13.r33.tokyjp05.jp.bb.gin.ntt.net [2001:218:0:2000::c6]
9 * 177 ms * ae-4.r25.lsanca07.us.bb.gin.ntt.net [2001:218:0:2000::62]
10 174 ms 186 ms 181 ms 2001:418:0:2::212 <---------------------------------------------------------- NTT America
11 176 ms 178 ms 181 ms 2001:418:0:4000::9e
12 319 ms 320 ms 328 ms 2001:668:0:2:ffff:0:8d88:6e9e <--------------------------------------------- Tinet GmbH
13 320 ms 327 ms 320 ms 2001:668:0:3:ffff:3:0:46
14 218 ms 217 ms 217 ms ethernetet-0-0-35-sr1.sgp1.constant.com [2001:19f0:fc00::a4f:1a1] <--- Vultr
15 320 ms 320 ms 321 ms ethernetswp55-ds1-u2-1155-a.sgp1.constant.com [2001:19f0:fc00::a4f:136]
16 * * * Request timed out.
17 320 ms 319 ms 320 ms 2001:19f0:4400:4001:5400:ff:fe32:b7e5

Trace complete.