To add further, whilst playing Apex I am getting packet loss, prediction error and congestion warnings. Intermittently I am getting errors when running international Speedtests which give a red frame and error message halfway through the test. So I have a suspicion that this is bigger than just PUBG AWS
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: What's the most interesting small town you've visited in South Africa?
Web Squad ISP
- Thread starter Gazed416
- Start date
- Status
PsyWulf
Honorary Master
- Joined
- Nov 22, 2006
- Messages
- 20,358
- Reaction score
- 16,003
2 restarts later. Vumatel Trenched. First reboot. Pings were all over. Second there was 2% packet loss to London. And now finally sorted
I assumed this was the ideal,been like this every time i've looked. Not rubberbanding though
Vuma Trenched Jhb North
Interestingly,WinMTR to the AWS IP my client is hitting,looks like after it hits AWS its a free for all pingwise,wouldn't be the first time network prioritization affects things less than ideally,especially with cloudbased providers
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.lan - 0 | 29 | 29 | 0 | 29 | 440 | 0 |
| as-vuma.jb-is-bry-01.za.ws.net.za - 0 | 29 | 29 | 2 | 45 | 478 | 2 |
| core.vuma-l3.jb1.za.ws.net.za - 0 | 29 | 29 | 2 | 43 | 464 | 11 |
| core.as-xe-02.jb1.za.ws.net.za - 0 | 29 | 29 | 1 | 36 | 391 | 2 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 29 | 29 | 1 | 35 | 367 | 2 |
| core.pe-xe-ix01.cp1.za.ws.net.za - 0 | 29 | 29 | 18 | 56 | 229 | 229 |
|aws-ge.tejb1-dxvif-fgv77f5d.cp1.za.ws.net.za - 0 | 29 | 29 | 19 | 68 | 231 | 181 |
| 52.95.106.132 - 0 | 29 | 29 | 20 | 70 | 303 | 91 |
| 52.93.57.126 - 4 | 29 | 28 | 20 | 92 | 380 | 91 |
| 52.93.57.131 - 4 | 29 | 28 | 20 | 99 | 352 | 134 |
| 54.239.46.83 - 0 | 29 | 29 | 315 | 404 | 653 | 424 |
| No response from host - 100 | 29 | 0 | 0 | 0 | 0 | 0 |
| 54.239.41.199 - 0 | 29 | 29 | 314 | 373 | 593 | 447 |
| 52.93.134.31 - 4 | 29 | 28 | 314 | 375 | 503 | 383 |
| 52.93.133.51 - 0 | 29 | 29 | 314 | 402 | 713 | 472 |
| 52.93.132.216 - 4 | 29 | 28 | 313 | 391 | 515 | 417 |
| 54.239.46.102 - 0 | 29 | 29 | 314 | 378 | 661 | 425 |
| No response from host - 100 | 29 | 0 | 0 | 0 | 0 | 0 |
| 52.93.12.126 - 0 | 29 | 29 | 315 | 371 | 562 | 345 |
| 52.93.12.107 - 0 | 29 | 29 | 314 | 382 | 662 | 340 |
| 52.93.13.30 - 0 | 29 | 29 | 315 | 428 | 1488 | 1488 |
| 52.93.13.57 - 4 | 29 | 28 | 315 | 439 | 1807 | 435 |
| 52.93.240.107 - 4 | 29 | 28 | 314 | 460 | 1683 | 472 |
| No response from host - 100 | 29 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )I am also in the same vicinity in North Riding with Evotel who use the same backhaul I believe as Vumatel, This makes me think that there is something going with our area/providers
Could you perhaps check your PUBG ping for me? Just interested to see if you're also hitting around 220ms
Evotel doesn’t use Vumatel. They use AEX, same as Vumatel Aerial. Vumatel trenched has their own dark backhaul back to Bryanston from JHB north. Complicated all round...
PsyWulf
Honorary Master
- Joined
- Nov 22, 2006
- Messages
- 20,358
- Reaction score
- 16,003
I'll download
Seeing the same erratic latency once we hit AWS’ network, which is why I believe AWS is experiencing an issue. Their SA network (even though I’m told it’s 400G transit to SA) is still being treated as their ugly duckling. I really hope the imminent DC launch will change that.
Logically the game will favour Singapore as it really is the closest ping wise for our JHB users. Weird that it’s behaving erratically though...
Will run a few extra tests. But from our end not seeing any local losses or issues. And things are routing as they should (except for the erratic AWS behaviour).
PsyWulf
Honorary Master
- Joined
- Nov 22, 2006
- Messages
- 20,358
- Reaction score
- 16,003
Snap,I see its paid for,no dosh to buy now
What doesn't make sense is that my friend on Cool Ideas in Johannesburg is getting the normal 175 - 180ms ping in PUBG through the same AWS servers. How could that be possible?
My guess is they've dampened their AWS direct connects in SA and using their peering at LINX rather. We don't have that capability yet (coming soon). If I dampen direct connect and peering, we'll pick them up on transit. Thing is, they peer with our transit providers in SA, so back to square 1.
Looks like one of our transit providers also turned them down. So when we turned AWS peering and direct connect down, logical route is peering in the EU.
At least that confirms a AWS issue. As I mentioned, their NOC make some of our big players look like they deliver awesome service. So doubtful we’ll get a response. Will try turn AWS up again on Monday and see if it’s fixed.
In the meanwhile, happy gaming!
Hi Websquadza, here's the MTR. I have submitted tickets and Carl has been very helpful in the past but he must be on leave as haven't gotten a response since 16/08/2019. Ticket number is 465448.
Code:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter - 1 | 380 | 379 | 0 | 16 | 108 | 0 |
| as-vuma.cp-gwf-03.za.ws.net.za - 0 | 380 | 380 | 0 | 15 | 109 | 0 |
| core.as-01.cp1.za.ws.net.za - 0 | 380 | 380 | 0 | 15 | 101 | 28 |
| core.cr-01.cp1.za.ws.net.za - 0 | 380 | 380 | 0 | 17 | 99 | 0 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 0 | 380 | 380 | 0 | 7 | 80 | 15 |
| 197.157.79.33 - 0 | 380 | 380 | 0 | 25 | 194 | 0 |
| No response from host - 100 | 380 | 0 | 0 | 0 | 0 | 0 |
| agr1-gwf-cr2-gi0-0-1.wolcomm.net - 1 | 380 | 379 | 0 | 10 | 111 | 0 |
| No response from host - 100 | 380 | 0 | 0 | 0 | 0 | 0 |
| 41.78.188.225 - 24 | 380 | 292 | 47038 | 4918 | 50705 | 49292 |
| agr1-lhx-cr1-te0-1-0.wolcomm.net - 0 | 380 | 380 | 134 | 156 | 240 | 156 |
|gi0-6-1-7.rcr21.b015533-1.lon01.atlas.cogentco.com - 4 | 380 | 368 | 140 | 186 | 334 | 156 |
| be2867.ccr22.lon01.atlas.cogentco.com - 3 | 380 | 372 | 147 | 189 | 467 | 156 |
| be2869.ccr42.lon13.atlas.cogentco.com - 4 | 380 | 368 | 148 | 186 | 243 | 172 |
| be2101.ccr32.bos01.atlas.cogentco.com - 3 | 380 | 369 | 201 | 246 | 350 | 278 |
| be3600.ccr22.alb02.atlas.cogentco.com - 4 | 380 | 366 | 205 | 253 | 1278 | 1278 |
| be2879.ccr22.cle04.atlas.cogentco.com - 4 | 380 | 367 | 219 | 269 | 362 | 282 |
| be2718.ccr42.ord01.atlas.cogentco.com - 3 | 380 | 372 | 234 | 276 | 338 | 297 |
| be2248.ccr22.ord03.atlas.cogentco.com - 3 | 380 | 372 | 228 | 270 | 349 | 281 |
|be2616.rcr21.b002281-5.ord03.atlas.cogentco.com - 2 | 380 | 374 | 226 | 272 | 373 | 295 |
| 169.254.0.0 - 2 | 379 | 373 | 229 | 258 | 363 | 276 |
| 10.255.18.171 - 2 | 379 | 372 | 222 | 252 | 319 | 255 |
| wotna3.login.wargaming.net - 4 | 379 | 367 | 228 | 257 | 313 | 255 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )Apex was fine earlier (was seeing 157 in JHB), but LoL has been painful tonight. Seeing between 200 and 300ms (also seen 400ms spikes) on EU west (usually around 160).
Downloads from the EU are still coming down around 60MB/s though (online.net server), and if I ping the same server I'm seeing the usual 160s. Tried doing a tracert to the LoL server but just got a bunch of no responses after the WS node.
Downloads from the EU are still coming down around 60MB/s though (online.net server), and if I ping the same server I'm seeing the usual 160s. Tried doing a tracert to the LoL server but just got a bunch of no responses after the WS node.
ISP cash cow
Executive Member
My vumatel aerial in Constanta kloof has just died? Anybody got any issues @websquadsa
Yes, international is "down" (or rather, at least to OVH & AT&T)
Code:
➜ ~ sudo mtr -wbc 10 12.0.1.28
Start: 2019-09-16T04:08:31+0200
HOST: BumbleBee.local Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.1.1.1 0.0% 10 0.3 0.3 0.2 0.4 0.1
2.|-- as-vuma.cp-gwf-4-01.za.ws.net.za (160.119.236.65) 0.0% 10 17.4 4.9 2.2 17.4 5.0
3.|-- 160.119.233.130 0.0% 10 2.7 2.9 2.2 6.3 1.2
4.|-- core.as-01.cp1.za.ws.net.za (160.119.233.169) 0.0% 10 1.0 1.0 1.0 1.1 0.0
5.|-- core.cr-01.cp1.za.ws.net.za (160.119.233.189) 0.0% 10 1.0 1.1 1.0 1.2 0.1
6.|-- core.pe-xe-ip01.cp1.za.ws.net.za (160.119.232.19) 0.0% 10 1.0 1.1 1.0 1.3 0.1
7.|-- 197.157.79.33 60.0% 10 2.0 2.4 1.9 3.7 0.9
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
9.|-- 197.157.79.33 90.0% 10 789.8 789.8 789.8 789.8 0.0
➜ ~ sudo mtr -wbc 10 www.ovh.com
Start: 2019-09-16T04:10:17+0200
HOST: BumbleBee.local Loss% Snt Last Avg Best Wrst StDev
1.|-- 10.1.1.1 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- as-vuma.cp-gwf-4-01.za.ws.net.za (160.119.236.65) 0.0% 10 2.4 3.8 2.1 14.2 3.7
3.|-- 160.119.233.130 0.0% 10 2.5 5.4 2.5 27.4 7.8
4.|-- core.as-01.cp1.za.ws.net.za (160.119.233.169) 0.0% 10 1.1 1.0 1.0 1.2 0.1
5.|-- core.cr-01.cp1.za.ws.net.za (160.119.233.189) 0.0% 10 1.1 2.0 1.0 6.3 1.8
6.|-- core.pe-xe-ip01.cp1.za.ws.net.za (160.119.232.19) 0.0% 10 1.2 1.3 1.1 2.5 0.5
7.|-- 197.157.79.33 20.0% 10 1.9 12.1 1.9 50.0 19.0
8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
➜ ~- Status