Web Squad ISP

Status
Not open for further replies.
3rd hop IP is 160.119.224.97 and pinging it show no drops though:

Ping statistics for 160.119.224.97:
Packets: Sent = 166, Received = 166, Lost = 0 (0% loss),

:unsure: *shrug*
 
abudabi said:
3rd hop IP is 160.119.224.97 and pinging it show no drops though:

Ping statistics for 160.119.224.97:
Packets: Sent = 166, Received = 166, Lost = 0 (0% loss),

:unsure: *shrug*
Click to expand...
abudabi said:
3rd hop IP is 160.119.224.97 and pinging it show no drops though:

Ping statistics for 160.119.224.97:
Packets: Sent = 166, Received = 166, Lost = 0 (0% loss),

:unsure: *shrug*
Click to expand...

Apologies for my delay here. 3rd hop is Vumatel's Bryanston Node - it's not necessarily good at replying to ICMP all the time, but definitely does the job it's meant to do and forwards packets without loss. When looking at an MTR, you want to see where the losses are commutative, ie, where loss at one hop leads to losses through the rest of the chain. If the next hop shows 0% loss, it just means that that specific hop either doesn't reply to all pings or doesn't respond to direct pings at all.

Only in your second MTR do I see a loss originate at 52.93.134.184 (AWS London Pop by the things of it - previous two hops are CPT and we hand over to AWS in JHB on 196.60.9.105 (peering). This is one of two things: actual packet loss on AWS transit routes or multipathing with AWS still using two very diverse routes (given WACS' instability). We have AWS direct connect in Cape Town, which is actually the return path for this traffic, so the local loop seems fine for now. Will keep an eye on this.
 
websquadza said:
Apologies for my delay here. 3rd hop is Vumatel's Bryanston Node - it's not necessarily good at replying to ICMP all the time, but definitely does the job it's meant to do and forwards packets without loss. When looking at an MTR, you want to see where the losses are commutative, ie, where loss at one hop leads to losses through the rest of the chain. If the next hop shows 0% loss, it just means that that specific hop either doesn't reply to all pings or doesn't respond to direct pings at all.

Only in your second MTR do I see a loss originate at 52.93.134.184 (AWS London Pop by the things of it - previous two hops are CPT and we hand over to AWS in JHB on 196.60.9.105 (peering). This is one of two things: actual packet loss on AWS transit routes or multipathing with AWS still using two very diverse routes (given WACS' instability). We have AWS direct connect in Cape Town, which is actually the return path for this traffic, so the local loop seems fine for now. Will keep an eye on this.
Click to expand...

No worries... I remembered a post by pbcool about cumalative loss soon after posting my story so I had a hunch it wasn't the case. My boy hasn't come running to complain again so it was probably just a momentary thing.

All good and thanks for the info. Hope you have a quiet easter weekend!
 
@websquadza - I want to finally make the switch from AH, but now that the lockdown's been extended I'm worried about someone not being available for the migration at the end of the month and being stuck without internet. Have you done any migrations from other ISPs for people on Octotel during the lockdown? Did all go smoothly?
 
Seeyou said:
@websquadza - I want to finally make the switch from AH, but now that the lockdown's been extended I'm worried about someone not being available for the migration at the end of the month and being stuck without internet. Have you done any migrations from other ISPs for people on Octotel during the lockdown? Did all go smoothly?
Click to expand...

It’s business as usual at Octotel and on our side. Month end is on a Thursday, which means we’ll be all hands on deck (Octotel too). No problems with migrations or installations (besides a shortage of CPEs on Octotel’s side). Also launched a StepUp on Octotel this week (double line for your first 6 months).
 
Hi guys, I am experiencing quite a lot of packet loss since last night, locally and internationally, anything you guys are aware of? Getting major rubber banding in COD Modern Warfare
 
Zodiak said:
Hi guys, I am experiencing quite a lot of packet loss since last night, locally and internationally, anything you guys are aware of? Getting major rubber banding in COD Modern Warfare
Click to expand...

No issues on the network. Sounds like it might be local loop again. Can you run an MTR?
 
Zodiak said:
Sure will be glad to run it, I have MTR open, what host do I put in?
Click to expand...

I’m not sure. Can you find an IP for a local gaming server first? That would be the easiest. (Check resource monitor in windows, it will tell you what IP you’re connecting to).
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 85 | 85 | 0 | 5 | 21 | 15 |
| core.as-02.jb1.za.ws.net.za - 0 | 85 | 85 | 2 | 10 | 26 | 18 |
| core.cr-xe-01.jb1.za.ws.net.za - 0 | 85 | 85 | 2 | 3 | 19 | 3 |
| core.pe-xe-ip01.jb1.za.ws.net.za - 0 | 85 | 85 | 2 | 3 | 18 | 3 |
| core.pe-xe-ip01.cp1.za.ws.net.za - 0 | 85 | 85 | 23 | 24 | 34 | 25 |
| 165-69-148-197.as37497.za.net - 0 | 85 | 85 | 23 | 24 | 28 | 25 |
| 162-68-148-197.as37497.za.net - 0 | 85 | 84 | 167 | 177 | 228 | 228 |
| 54-71-148-197.as37497.za.net - 0 | 85 | 84 | 165 | 174 | 206 | 173 |
| 33-66-148-197.as37497.za.net - 0 | 84 | 84 | 165 | 182 | 327 | 175 |
| 195.66.226.234 - 0 | 84 | 84 | 167 | 180 | 228 | 206 |
| ae1-br01-eqld5.as57976.net - 4 | 84 | 81 | 173 | 177 | 198 | 174 |
| et-0-0-2-br02-eqam1.as57976.net - 3 | 84 | 82 | 172 | 189 | 461 | 258 |
| 137.221.78.83 - 6 | 84 | 79 | 173 | 184 | 220 | 186 |
| 185.60.112.157 - 5 | 84 | 80 | 172 | 182 | 257 | 175 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
 
Zodiak said:
| 195.66.226.234 - 0 | 84 | 84 | 167 | 180 | 228 | 206 |
| ae1-br01-eqld5.as57976.net - 4 | 84 | 81 | 173 | 177 | 198 | 174 |
| et-0-0-2-br02-eqam1.as57976.net - 3 | 84 | 82 | 172 | 189 | 461 | 258 |
| 137.221.78.83 - 6 | 84 | 79 | 173 | 184 | 220 | 186 |
| 185.60.112.157 - 5 | 84 | 80 | 172 | 182 | 257 | 175 |
|________________________________________________|______|______|______|______|______|______|
WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( [email protected] )
Click to expand...
Blizzard busting up their routes again from London looks like
 
Eish, I'm having real issues now, showing 250% packet loss and get disconnected from the Blizzard server and kicked out from the game entirely.....
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X