Web Squad ISP

Status
Not open for further replies.
Kryptonite said:
It's the Tier 2 ISP thats the problem...............what must i do, report it on your peering partners behalf, look at the trace i provided.

1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.25.2 0.0% 10 0.7 1.2 0.6 4.4 1.1
3.|-- Blizzard 0.0% 10 0.9 0.9 0.8 1.1 0.0
4.|-- 137.221.66.32 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.77.76 0.0% 10 21.9 36.7 0.9 190.0 63.5
6.|-- 137.221.77.32 0.0% 10 1.0 1.2 1.0 2.6 0.3
7.|-- et-4-0-14.edge7.Paris1.Level3.net 10.0% 10 10.3 5.1 1.1 10.3 3.7
8.|-- ae2.3210.ear4.London2.level3.net 10.0% 10 8.4 8.4 8.3 8.6 0.0
9.|-- NETWORK-PLA.ear4.London2.Level3.net 0.0% 10 8.4 8.4 8.3 8.5 0.0
10.|-- 53-71-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 148.6 0.0
11.|-- 161-68-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 149.0 0.0
12.|-- 166-69-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 148.6 0.0
13.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 148.6 148.6 148.5 148.7 0.0
14.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 153.2 156.8 150.3 167.7 6.3
Click to expand...

Hop 13 and 14 clearly show 0% loss. That means 0% loss from blizzard’s server’s to our core and Vumatel handover in Cape Town. I can’t see what happens beyond this point because your router’s ICMP is disabled. Just to be 100% clear, there is 0 loss between blizzard and our network according to these results. If you see loss on Intermediate hops, that’s because those devices may not respond to ICMP requests. But seeing as it does not carry through to the last visible hop, this MTR is clear.
 
**** me, are you serious?
7.|-- et-4-0-14.edge7.Paris1.Level3.net 10.0% 10 10.3 5.1 1.1 10.3 3.7
8.|-- ae2.3210.ear4.London2.level3.net 10.0% 10 8.4 8.4 8.3 8.6 0.0

That's the problem there, do you report it or must I, do you not have upstream partners you report loss to?
 
and yes my routers ICMP is disabled for good reason i am sure you understand.........you knows....DDOS and such
 
Kryptonite said:
**** me, are you serious?
7.|-- et-4-0-14.edge7.Paris1.Level3.net 10.0% 10 10.3 5.1 1.1 10.3 3.7
8.|-- ae2.3210.ear4.London2.level3.net 10.0% 10 8.4 8.4 8.3 8.6 0.0

That's the problem there, do you report it or must I, do you not have upstream partners you report loss to?
Click to expand...
This is not packet loss. It is a device that has some sort of ICMP rate limiting on it which is 100% normal. You disable your ICMP altogether, this device limits the requests - different sides of the same coin. As I've said, that packet loss does not carry through to the last hop. There are dozens of threads on this forum explaining how to read a MTR. If the loss does not carry through to the last hop, it is not packet loss.

To explain how MTRs work: MTRs use the traceroute protocol to identify all the hops a packet may take from A to B. It then sets up individual ICMP sessions to each of those hops (IE pings them each directly). It does not track the actual flow of a single packet from A to B. This can be inferred by the packet performance at the last hop and why some hops sometimes drop packets, or have varying latencies. When loss is picked up on the last hop, we work backwards to see which hop it could originate on by seeing where it originates and starts carrying through the test.

Kryptonite said:
and yes my routers ICMP is disabled for good reason i am sure you understand.........you knows....DDOS and such
Click to expand...
I did not ask you to enable ICMP - I asked you to run a MTR from your PC to somewhere so we can see how packets perform on your first hop (the inverse of the results you keep posting, blizzard's last hop).. To be clear, the reason our support, and I, have asked for a MTR from your PC to anywhere is to see if we can pick up packet loss on the one hop we cannot see, the hop from your router to Vumatel.

Just in case, you know, you don't trust your ISP to share with you how an MTR works, I'm sharing the first result from the Google search "reading an MTR test" - I think this should be an objective enough summary: https://www.exavault.com/blog/reading-mtr-output (there's an explanation under the second section - Single occurrence packet loss)
 
Last edited:
Kryptonite said:
It's the Tier 2 ISP thats the problem...............what must i do, report it on your peering partners behalf, look at the trace i provided.

1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.25.2 0.0% 10 0.7 1.2 0.6 4.4 1.1
3.|-- Blizzard 0.0% 10 0.9 0.9 0.8 1.1 0.0
4.|-- 137.221.66.32 0.0% 10 0.4 0.5 0.4 0.7 0.0
5.|-- 137.221.77.76 0.0% 10 21.9 36.7 0.9 190.0 63.5
6.|-- 137.221.77.32 0.0% 10 1.0 1.2 1.0 2.6 0.3
7.|-- et-4-0-14.edge7.Paris1.Level3.net 10.0% 10 10.3 5.1 1.1 10.3 3.7
8.|-- ae2.3210.ear4.London2.level3.net 10.0% 10 8.4 8.4 8.3 8.6 0.0
9.|-- NETWORK-PLA.ear4.London2.Level3.net 0.0% 10 8.4 8.4 8.3 8.5 0.0
10.|-- 53-71-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 148.6 0.0
11.|-- 161-68-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 149.0 0.0
12.|-- 166-69-148-197.as37497.za.net 0.0% 10 148.5 148.5 148.4 148.6 0.0
13.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 148.6 148.6 148.5 148.7 0.0
14.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 153.2 156.8 150.3 167.7 6.3
Click to expand...
That trace looks clean, loss doesn't carry to the final destination, it's just ICMP rate limiting.
 
Hey @websquadza, thanks for the effort last night :)
Have to say, never seen an ISP go as far as config a custom client Mikrotik device 21:00 on a Saturday night :ROFL:
Well done!

Everything seems well, and the connection is stable at ~525 Mbps. Massive jump from ~360 Mbps :) Thanks!

13069793694.png


1650778330762.png
 
Last edited:
Grassnyer said:
Hey @websquadza, thanks for the effort last night :)
Have to say, never seen an ISP go as far as config a custom client Mikrotik device 21:00 on a Saturday night :ROFL:
Well done!

Everything seems well, and the connection is stable at ~525 Mbps. Massive jump from ~360 Mbps :) Thanks!

13069793694.png


View attachment 1297298
Click to expand...

Thanks for the feedback! Good to know it helped.
 
Last edited:
next door neighbour, same vumatel, different ISP, clean.........this ISP, not clean. There is something wrong with the path this traffic takes.
 
Kryptonite said:
next door neighbour, same vumatel, different ISP, clean.........this ISP, not clean. There is something wrong with the path this traffic takes.
Click to expand...
Nothing wrong on the path- Level 3 is two AS hops away and they do limit ICMP. Please run the 1 test we’ve asked you to provide. It’s not a difficult test. Your only test provided shows 0% packet loss. And by definition in the last post- we need results on your last mile, not on core. If the only test you’ve supplied us shows 0% loss to the hop before yours, it stands to reason the issue could be on your line, at your CPE or your router. None of that infrastructure is shared with your neighbour.
 
Perhaps that 3rd hop? I am seeing ERRORS on my WAN connection on the router but i cannot tell you what they are, about 40 over the past 90 minutes, so it's incrementing.

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms <1 ms 160.119.236.1
3 17 ms 120 ms 47 ms 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 19 ms 19 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 3 ms 15 ms 21 ms 160.119.236.1
3 56 ms 6 ms 9 ms 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 20 ms 20 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99
 
hmmm, timeouts on that 3rd hop.

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 160.119.236.1
3 3 ms 2 ms * 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 20 ms 20 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99

Trace complete.

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 160.119.236.1
3 4 ms 22 ms 91 ms 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 20 ms 19 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99
 
I feel like @websquadza is going to throw me with bricks. We finally sorted out the OpenServe issue, but Metro fibre will release 1 Gbps and really keen on trying that :ROFL:

What is the process of moving between FNOs? What are the costs involved?
 
Kryptonite said:
hmmm, timeouts on that 3rd hop.

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 160.119.236.1
3 3 ms 2 ms * 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 20 ms 20 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99

Trace complete.

Tracing route to www.google.co.za [172.217.170.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms 1 ms 1 ms 160.119.236.1
3 4 ms 22 ms 91 ms 160.119.233.132
4 1 ms 1 ms 1 ms 160.119.233.161
5 19 ms 19 ms 19 ms 160.119.232.117
6 20 ms 20 ms 20 ms 196.60.9.113
7 19 ms 19 ms 19 ms 172.253.65.179
8 20 ms 20 ms 19 ms 142.251.51.219
9 19 ms 19 ms 19 ms 172.217.170.99
Click to expand...

MTR please. Instructions are on your ticket.

And once again - if it’s not on the last hop, it’s not an issue.
 
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter - 0 | 44 | 44 | 0 | 0 | 0 | 0 |
| as-vuma.cp-is-br-01.za.ws.net.za - 0 | 44 | 44 | 0 | 12 | 99 | 1 |
| 160.119.233.132 - 10 | 32 | 29 | 2 | 11 | 55 | 41 |
| core.as-01.cp1.za.ws.net.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| 160.119.232.117 - 3 | 40 | 39 | 19 | 19 | 20 | 19 |
| 196-60-9-113.ixp.joburg - 0 | 44 | 44 | 19 | 20 | 21 | 20 |
| 172.253.65.179 - 0 | 44 | 44 | 19 | 19 | 19 | 19 |
| 172.253.65.253 - 0 | 44 | 44 | 20 | 20 | 24 | 20 |
| dns.google - 0 | 44 | 44 | 19 | 19 | 19 | 19 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
 
Kryptonite said:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dlinkrouter - 0 | 44 | 44 | 0 | 0 | 0 | 0 |
| as-vuma.cp-is-br-01.za.ws.net.za - 0 | 44 | 44 | 0 | 12 | 99 | 1 |
| 160.119.233.132 - 10 | 32 | 29 | 2 | 11 | 55 | 41 |
| core.as-01.cp1.za.ws.net.za - 0 | 44 | 44 | 1 | 1 | 2 | 1 |
| 160.119.232.117 - 3 | 40 | 39 | 19 | 19 | 20 | 19 |
| 196-60-9-113.ixp.joburg - 0 | 44 | 44 | 19 | 20 | 21 | 20 |
| 172.253.65.179 - 0 | 44 | 44 | 19 | 19 | 19 | 19 |
| 172.253.65.253 - 0 | 44 | 44 | 20 | 20 | 24 | 20 |
| dns.google - 0 | 44 | 44 | 19 | 19 | 19 | 19 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...
That MTR looks 100% clear (last hop shows no loss that could carry on from an earlier hop). You're welcome to run this to a Blizzard IP to confirm. Try running this when whatever service you're struggling with acts up. I remember you saying you were struggling with Youtube and some other services last week; likely related.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X