wingnut771
Honorary Master
not as bad as last night, at least stuff isn't buffering:
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Thanks

Guys, my ping issues to EU are back with a vengence today, was fine up until and including yesterday, PUBG ping fluctuates from 180ms all the way to 260ms in every match this afternoon and even Speedtest to Coreix London servers on over 200ms and usually at 160ms, so quite a hike in latency and international speeds not fantastic either.... Nothing downloading in the background and I am on direct LAN to the router:
![]()
Ok, seems it's all back to normal again after an hour
Seems like we went live on the new transit provider? Things went a little wonky last night and now I see new routes... Looking good....
And my line is down again.. Anyone else vumatel trenched kzn... Flashing green on cpe box
Thanks, didn't check when it came back online, saw it as a sign I should go to bedVumatel issue early this morning (00:36 lasting just under 9 mins). Didn't receive any network notices from Vumatel, but saw traffic on our NNI drop for a few mins then come back up.
fibre in this country seems more unstable than blinking adsl. Daily I see a flashing green light on the box with disconnects.Flashing green is usually upstreamThanks, didn't check when it came back online, saw it as a sign I should go to bedfibre in this country seems more unstable than blinking adsl. Daily I see a flashing green light on the box with disconnects.

The .co.uk site hosting bounces from London to New York to Blizzard's main hub and then a few extra hops,though Webserver hosting does not a good test make@websquadza
Hi Carl,
Our games tonight have an extremely high ping compared to normal (we play EU servers) it seems that we are being routed through the U.S. Is there a reason for this or a way to fix it.
View attachment 717605
Serious buffering happening and running a speedtest at 10:30 in the morning yielded this result which is rather bleak to say the least. This is with vpn off.. With vpn on I max out at 18Mbps. No matter what server I choose in new York.![]()
Even running those tests, still going through NY, but I'm not sure @websquadza can actually do anything about it.The .co.uk site hosting bounces from London to New York to Blizzard's main hub and then a few extra hops,though Webserver hosting does not a good test make
Rather try the IPs from their support pages
EU Tracert
Tracing route to 185.60.112.157 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 2 ms 2 ms 1 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
5 3 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
6 5 ms 1 ms 2 ms v101.core2.bcn1.he.net [216.66.90.117]
7 178 ms 158 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113]
8 226 ms 226 ms 226 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166]
9 225 ms 225 ms 225 ms eqix-ix-ny8.blizzard.com [198.32.118.87]
10 236 ms 241 ms 242 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
11 234 ms 234 ms 234 ms xe-0-0-0-1-br01-eqld5.as57976.net [137.221.65.25]
12 243 ms 232 ms 233 ms et-0-0-2-br02-eqam1.as57976.net [137.221.65.91]
13 233 ms 233 ms 232 ms et-0-0-67-pe01-eqam1.as57976.net [137.221.78.71]
14 234 ms 234 ms 234 ms 137.221.66.43
15 233 ms 234 ms 233 ms 185.60.112.157
Tracing route to 185.60.114.159 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 1 ms 1 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
5 1 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
6 1 ms 1 ms 1 ms v101.core2.bcn1.he.net [216.66.90.117]
7 158 ms 161 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113]
8 243 ms 241 ms 257 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166]
9 225 ms 224 ms 224 ms eqix-ix-ny8.blizzard.com [198.32.118.87]
10 232 ms 232 ms 232 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
11 232 ms 233 ms 232 ms xe-0-0-0-1-br01-eqld5.as57976.net [137.221.65.25]
12 245 ms 241 ms 237 ms et-0-0-29-br02-eqld5.as57976.net [137.221.65.23]
13 * * 1315 ms et-0-0-2-br02-eqpa4.as57976.net [137.221.65.18]
14 233 ms 233 ms 234 ms be2-pe01-eqpa4.as57976.net [137.221.77.71]
15 240 ms 235 ms 232 ms 185.60.114.159
US Tracert
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms * 7 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1]
3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89]
4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29]
5 1 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18]
6 2 ms 1 ms 1 ms v101.core2.bcn1.he.net [216.66.90.117]
7 159 ms 165 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113]
8 225 ms 225 ms 224 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166]
9 227 ms 224 ms 224 ms eqix-ix-ny8.blizzard.com [198.32.118.87]
10 317 ms 286 ms 286 ms ae1-br01-eqny8.as57976.net [137.221.71.33]
11 283 ms 287 ms 284 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8]
12 285 ms 284 ms 284 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2]
13 291 ms 286 ms 285 ms 137.221.65.132
14 284 ms 284 ms 284 ms et-0-0-31-pe01-swlv10.as57976.net [137.221.83.67]
15 283 ms 284 ms 284 ms las-swlv10-ia-bons-02.as57976.net [137.221.66.19]
16 284 ms 286 ms 289 ms 137.221.105.2
Even running those tests, still going through NY, but I'm not sure @websquadza can actually do anything about it.
Code:EU Tracert Tracing route to 185.60.112.157 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 2 ms 2 ms 1 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1] 3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89] 4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29] 5 3 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18] 6 5 ms 1 ms 2 ms v101.core2.bcn1.he.net [216.66.90.117] 7 178 ms 158 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113] 8 226 ms 226 ms 226 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166] 9 225 ms 225 ms 225 ms eqix-ix-ny8.blizzard.com [198.32.118.87] 10 236 ms 241 ms 242 ms ae1-br01-eqny8.as57976.net [137.221.71.33] 11 234 ms 234 ms 234 ms xe-0-0-0-1-br01-eqld5.as57976.net [137.221.65.25] 12 243 ms 232 ms 233 ms et-0-0-2-br02-eqam1.as57976.net [137.221.65.91] 13 233 ms 233 ms 232 ms et-0-0-67-pe01-eqam1.as57976.net [137.221.78.71] 14 234 ms 234 ms 234 ms 137.221.66.43 15 233 ms 234 ms 233 ms 185.60.112.157 Tracing route to 185.60.114.159 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 3 ms 1 ms 1 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1] 3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89] 4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29] 5 1 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18] 6 1 ms 1 ms 1 ms v101.core2.bcn1.he.net [216.66.90.117] 7 158 ms 161 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113] 8 243 ms 241 ms 257 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166] 9 225 ms 224 ms 224 ms eqix-ix-ny8.blizzard.com [198.32.118.87] 10 232 ms 232 ms 232 ms ae1-br01-eqny8.as57976.net [137.221.71.33] 11 232 ms 233 ms 232 ms xe-0-0-0-1-br01-eqld5.as57976.net [137.221.65.25] 12 245 ms 241 ms 237 ms et-0-0-29-br02-eqld5.as57976.net [137.221.65.23] 13 * * 1315 ms et-0-0-2-br02-eqpa4.as57976.net [137.221.65.18] 14 233 ms 233 ms 234 ms be2-pe01-eqpa4.as57976.net [137.221.77.71] 15 240 ms 235 ms 232 ms 185.60.114.159 US Tracert Tracing route to 137.221.105.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 8 ms * 7 ms as-vuma.jb-is-pld-01.za.ws.net.za [160.119.228.1] 3 1 ms 1 ms 1 ms core.as-xe-02.jb1.za.ws.net.za [160.119.224.89] 4 1 ms 1 ms 1 ms core.cr-xe-01.jb1.za.ws.net.za [160.119.224.29] 5 1 ms 1 ms 1 ms core.pe-xe-ip01.jb1.za.ws.net.za [160.119.224.18] 6 2 ms 1 ms 1 ms v101.core2.bcn1.he.net [216.66.90.117] 7 159 ms 165 ms 158 ms 10ge2-11.core1.lon2.he.net [184.104.192.113] 8 225 ms 225 ms 224 ms 100ge13-2.core1.nyc4.he.net [72.52.92.166] 9 227 ms 224 ms 224 ms eqix-ix-ny8.blizzard.com [198.32.118.87] 10 317 ms 286 ms 286 ms ae1-br01-eqny8.as57976.net [137.221.71.33] 11 283 ms 287 ms 284 ms et-0-0-2-br02-eqch2.as57976.net [137.221.65.8] 12 285 ms 284 ms 284 ms et-0-0-29-br01-eqch2.as57976.net [137.221.65.2] 13 291 ms 286 ms 285 ms 137.221.65.132 14 284 ms 284 ms 284 ms et-0-0-31-pe01-swlv10.as57976.net [137.221.83.67] 15 283 ms 284 ms 284 ms las-swlv10-ia-bons-02.as57976.net [137.221.66.19] 16 284 ms 286 ms 289 ms 137.221.105.2
Tests from their looking glass show the same route doing a 'reverse' test (their network to my ip)
Will do those packet captures tonight