South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Yar little weird - If I enable IPv6 in WoW I get higher ping than without. About ~17-20ms difference (151ms vs 168ms).
Target Name: 2a04:e800:5016:2073:f816:5bff:fe05:74dd
IP: 2a04:e800:5016:2073:f816:5bff:fe05:74dd
Date/Time: 06 Aug 2020 14:00:10 - 06 Aug 2020 14:10:10
Hop Sent PL% Min Max Avg Host Name / [IP]
1 36 0 0,37 4,00 0,66 2c0f:f030:1200:200:: [2c0f:f030:1200:200::]
2 36 3 2,69 4,98 3,55 2c0f:f030:1300::1 [2c0f:f030:1300::1]
3 36 0 2,84 6,03 3,45 core.cr-01.cp1.za.ws.net.za [2c0f:f030:1000::201]
4 36 0 2,96 13,62 4,52 2c0f:f9e8:a00:6::1 [2c0f:f9e8:a00:6::1]
5 36 0 2,92 18,67 4,47 2c0f:f9e8:0:5::2 [2c0f:f9e8:0:5::2]
6 36 0 144,37 211,08 148,57 2c0f:f9e8:0:c::2 [2c0f:f9e8:0:c::2]
7 36 0 144,53 163,84 146,57 2c0f:f9e8:0:9::1 [2c0f:f9e8:0:9::1]
8 36 0 145,87 189,25 149,04 2001:7f8:4::e278:1 [2001:7f8:4::e278:1]
9 36 0 167,23 357,92 212,47 ae1-br01-eqld5.as57976.net [2a04:e802:e:6000::33]
10 36 100 0 0 0 [-]
11 36 0 167,15 252,18 171,38 2a04:e802:d:6000::83 [2a04:e802:d:6000::83]
12 36 0 167,45 172,12 168,52 2a04:e802:2:6:5016::1 [2a04:e802:2:6:5016::1]
13 36 0 167,71 175,65 168,91 2a04:e800:5016:6000::11 [2a04:e800:5016:6000::11]
14 36 0 167,05 171,93 167,81 2a04:e800:5016:2073:f816:5bff:fe05:74dd [2a04:e800:5016:2073:f816:5bff:fe05:74dd]
I just noticed a slight difference and wondered why. Not a biggie to keep it disabledCode:Target Name: 2a04:e800:5016:2073:f816:5bff:fe05:74dd IP: 2a04:e800:5016:2073:f816:5bff:fe05:74dd Date/Time: 06 Aug 2020 14:00:10 - 06 Aug 2020 14:10:10 Hop Sent PL% Min Max Avg Host Name / [IP] 1 36 0 0,37 4,00 0,66 2c0f:f030:1200:200:: [2c0f:f030:1200:200::] 2 36 3 2,69 4,98 3,55 2c0f:f030:1300::1 [2c0f:f030:1300::1] 3 36 0 2,84 6,03 3,45 core.cr-01.cp1.za.ws.net.za [2c0f:f030:1000::201] 4 36 0 2,96 13,62 4,52 2c0f:f9e8:a00:6::1 [2c0f:f9e8:a00:6::1] 5 36 0 2,92 18,67 4,47 2c0f:f9e8:0:5::2 [2c0f:f9e8:0:5::2] 6 36 0 144,37 211,08 148,57 2c0f:f9e8:0:c::2 [2c0f:f9e8:0:c::2] 7 36 0 144,53 163,84 146,57 2c0f:f9e8:0:9::1 [2c0f:f9e8:0:9::1] 8 36 0 145,87 189,25 149,04 2001:7f8:4::e278:1 [2001:7f8:4::e278:1] 9 36 0 167,23 357,92 212,47 ae1-br01-eqld5.as57976.net [2a04:e802:e:6000::33] 10 36 100 0 0 0 [-] 11 36 0 167,15 252,18 171,38 2a04:e802:d:6000::83 [2a04:e802:d:6000::83] 12 36 0 167,45 172,12 168,52 2a04:e802:2:6:5016::1 [2a04:e802:2:6:5016::1] 13 36 0 167,71 175,65 168,91 2a04:e800:5016:6000::11 [2a04:e800:5016:6000::11] 14 36 0 167,05 171,93 167,81 2a04:e800:5016:2073:f816:5bff:fe05:74dd [2a04:e800:5016:2073:f816:5bff:fe05:74dd]![]()
Yep normal EU ping is awesome atm. Smooth SailingWill look into this, looks to be upstream; I see EU is at 148ms which is good, but there's a big spike as we reach Blizzard's network.
Had to change over to Google's DNS servers this morning. Was getting some crazy slow (seconds, not milliseconds) DNS query resolutions from Cloudflare since they disabled the CPT hosting.
Had to change over to Google's DNS servers this morning. Was getting some crazy slow (seconds, not milliseconds) DNS query resolutions from Cloudflare since they disabled the CPT hosting.
Seems they struggle to manage loads once one pop goes down. Have you tried quad9?
Fine for me in Durban.Internet dead?
Seems to be a Vumatel issue affecting JHB users across the board. Waiting for feedback from their NOC
Not the whole of joburg. Our probes on certain pops (specifically the Bryanston master node) are up.