Web Squad ISP

Status
Not open for further replies.
There's definitely an intermittent issue on your routes to France, I can see in Wow TBC classic i get major latency spikes but discord etc all work fine. It's pretty much going to mean a change in ISP's if you guys cant sort this out as another ZA person in the same area as me doesnt experience it, only difference is they are on Openserve so here's the path we talking about. Happens about once every 20 - 30 minutes, between 5-30 seconds of just no comms. It's really a problem as in a 4 hour space you have 8 major spikes and it kills the game.

TRACEROUTE:
traceroute to xxxxxxx, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.380 ms 0.375 ms 0.375 ms
2 37.244.25.2 (37.244.25.2) 1.111 ms 1.108 ms 1.317 ms
3 Blizzard Blizzard 1.294 ms 1.302 ms 1.298 ms
4 137.221.66.32 (137.221.66.32) 1.063 ms 1.071 ms 1.070 ms
5 137.221.77.76 (137.221.77.76) 7.568 ms 7.568 ms 7.568 ms
6 137.221.65.35 (137.221.65.35) 7.529 ms 7.711 ms 7.663 ms
7 137.221.65.19 (137.221.65.19) 7.710 ms 7.696 ms 7.708 ms
8 137.221.79.34 (137.221.79.34) 55.700 ms 51.699 ms 51.661 ms
9 195.66.224.25 (195.66.224.25) 8.172 ms 8.184 ms 8.179 ms
10 197.148.66.42 (197.148.66.42) 8.992 ms 8.970 ms 8.210 ms
11 13-71-148-197.as37497.za.net (197.148.71.13) 151.012 ms 151.032 ms 151.010 ms
12 161-68-148-197.as37497.za.net (197.148.68.161) 150.979 ms 151.018 ms 150.990 ms
13 166-69-148-197.as37497.za.net (197.148.69.166) 150.970 ms 150.948 ms 150.941 ms
14 core.cr-01.cp1.za.ws.net.za (160.119.232.5) 151.035 ms 150.783 ms 150.765 ms
15 xxxxxxxxx xxxxxx 170.886 ms 159.180 ms 159.306 ms
 
Last edited by a moderator:
Kryptonite said:
There's definitely an intermittent issue on your routes to France, I can see in Wow TBC classic i get major latency spikes but discord etc all work fine. It's pretty much going to mean a change in ISP's if you guys cant sort this out as another ZA person in the same area as me doesnt experience it, only difference is they are on Openserve so here's the path we talking about. Happens about once every 20 - 30 minutes, between 5-30 seconds of just no comms. It's really a problem as in a 4 hour space you have 8 major spikes and it kills the game.

TRACEROUTE:
traceroute to 160.119.236.32 (160.119.236.32), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.380 ms 0.375 ms 0.375 ms
2 37.244.25.2 (37.244.25.2) 1.111 ms 1.108 ms 1.317 ms
3 Blizzard Blizzard 1.294 ms 1.302 ms 1.298 ms
4 137.221.66.32 (137.221.66.32) 1.063 ms 1.071 ms 1.070 ms
5 137.221.77.76 (137.221.77.76) 7.568 ms 7.568 ms 7.568 ms
6 137.221.65.35 (137.221.65.35) 7.529 ms 7.711 ms 7.663 ms
7 137.221.65.19 (137.221.65.19) 7.710 ms 7.696 ms 7.708 ms
8 137.221.79.34 (137.221.79.34) 55.700 ms 51.699 ms 51.661 ms
9 195.66.224.25 (195.66.224.25) 8.172 ms 8.184 ms 8.179 ms
10 197.148.66.42 (197.148.66.42) 8.992 ms 8.970 ms 8.210 ms
11 13-71-148-197.as37497.za.net (197.148.71.13) 151.012 ms 151.032 ms 151.010 ms
12 161-68-148-197.as37497.za.net (197.148.68.161) 150.979 ms 151.018 ms 150.990 ms
13 166-69-148-197.as37497.za.net (197.148.69.166) 150.970 ms 150.948 ms 150.941 ms
14 core.cr-01.cp1.za.ws.net.za (160.119.232.5) 151.035 ms 150.783 ms 150.765 ms
15 as-vuma.cp-is-br-01.za.ws.net.za (160.119.233.166) 170.886 ms 159.180 ms 159.306 ms
Click to expand...

Can you get an MTR rather than a trace so we can escalate to the upstream? Also consider editing out your IP from this trace.

Edit, can you please open a ticket with support? We're seeing something this side and believe it may be related to you.
 
Last edited:
MTR:
Start: Mon Feb 14 05:56:51 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.25.2 0.0% 10 0.9 0.9 0.6 1.9 0.0
3.|-- Blizzard 0.0% 10 1.0 1.0 0.8 1.2 0.0
4.|-- 137.221.66.32 0.0% 10 0.5 1.0 0.4 5.5 1.6
5.|-- 137.221.77.76 0.0% 10 7.5 23.0 7.4 155.0 46.4
6.|-- 137.221.65.35 0.0% 10 8.7 17.1 7.3 42.5 15.2
7.|-- 137.221.65.19 0.0% 10 7.5 7.5 7.4 7.6 0.0
8.|-- 137.221.79.34 0.0% 10 7.7 11.4 7.5 45.3 11.9
9.|-- 195.66.224.25 0.0% 10 8.1 8.1 8.0 8.2 0.0
10.|-- 197.148.66.42 0.0% 10 8.1 8.1 8.0 8.2 0.0
11.|-- 13-71-148-197.as37497.za.net 0.0% 10 150.9 150.9 150.8 151.0 0.0
12.|-- 161-68-148-197.as37497.za.net 0.0% 10 151.0 150.9 150.8 151.0 0.0
13.|-- 166-69-148-197.as37497.za.net 0.0% 10 151.0 150.9 150.8 151.0 0.0
14.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 150.9 150.9 150.8 151.0 0.0
15.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 186.7 166.9 153.3 211.0 19.6


14/02/2022 05:56:51 UTC
--------------------

MTR:
Start: Mon Feb 14 05:56:51 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.7 0.0
2.|-- 37.244.24.131 0.0% 10 0.8 1.0 0.6 3.2 0.7
3.|-- Blizzard 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.46 0.0% 10 3.3 3.4 0.5 17.5 5.6
5.|-- 137.221.78.52 0.0% 10 1.1 1.1 1.0 1.2 0.0
6.|-- 137.221.65.74 0.0% 10 1.1 3.2 1.0 21.0 6.2
7.|-- 137.221.78.32 0.0% 10 1.3 1.3 1.1 1.5 0.0
8.|-- 80.249.213.88 0.0% 10 7.5 7.4 7.2 7.8 0.0
9.|-- 13-71-148-197.as37497.za.net 0.0% 10 150.2 150.2 150.1 150.4 0.0
10.|-- 161-68-148-197.as37497.za.net 0.0% 10 150.3 150.2 150.1 150.4 0.0
11.|-- 166-69-148-197.as37497.za.net 0.0% 10 150.2 150.2 150.0 150.2 0.0
12.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 150.3 150.3 150.2 150.4 0.0
13.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 158.6 157.7 152.0 176.3 7.5

Here is the MTR, each time i test, it looks fine and because it's so intermittent, we never catch it but it's really bad.
 
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 881 | 881 | 0 | 0 | 26 | 0 |

| 160.119.237.127 - 1 | 878 | 877 | 0 | 1 | 26 | 0 |

| 102.220.48.29 - 0 | 880 | 880 | 1 | 3 | 165 | 2 |

| 160.119.232.161 - 1 | 877 | 876 | 1 | 2 | 46 | 3 |

| 160.119.232.86 - 1 | 869 | 866 | 24 | 25 | 132 | 26 |

| 197.148.69.165 - 1 | 861 | 856 | 24 | 26 | 89 | 24 |

| 197.148.68.162 - 1 | 857 | 851 | 27 | 28 | 91 | 28 |

| 197.148.71.14 - 1 | 857 | 851 | 170 | 171 | 234 | 170 |

| 197.148.66.41 - 1 | 861 | 856 | 170 | 171 | 234 | 170 |

| 195.66.226.234 - 1 | 862 | 857 | 171 | 176 | 270 | 182 |

| 137.221.79.33 - 3 | 802 | 783 | 177 | 226 | 3519 | 186 |

| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |

| 137.221.65.77 - 6 | 707 | 666 | 177 | 260 | 3519 | 180 |

| 137.221.78.55 - 1 | 861 | 856 | 177 | 179 | 241 | 179 |

| 185.60.112.157 - 1 | 857 | 851 | 177 | 178 | 241 | 179 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This is to a retail Wow server. Drops are happening every 20-30 mins and last between 1 and 2 minutes.
 
S7wede said:
|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 881 | 881 | 0 | 0 | 26 | 0 |

| 160.119.237.127 - 1 | 878 | 877 | 0 | 1 | 26 | 0 |

| 102.220.48.29 - 0 | 880 | 880 | 1 | 3 | 165 | 2 |

| 160.119.232.161 - 1 | 877 | 876 | 1 | 2 | 46 | 3 |

| 160.119.232.86 - 1 | 869 | 866 | 24 | 25 | 132 | 26 |

| 197.148.69.165 - 1 | 861 | 856 | 24 | 26 | 89 | 24 |

| 197.148.68.162 - 1 | 857 | 851 | 27 | 28 | 91 | 28 |

| 197.148.71.14 - 1 | 857 | 851 | 170 | 171 | 234 | 170 |

| 197.148.66.41 - 1 | 861 | 856 | 170 | 171 | 234 | 170 |

| 195.66.226.234 - 1 | 862 | 857 | 171 | 176 | 270 | 182 |

| 137.221.79.33 - 3 | 802 | 783 | 177 | 226 | 3519 | 186 |

| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |

| 137.221.65.77 - 6 | 707 | 666 | 177 | 260 | 3519 | 180 |

| 137.221.78.55 - 1 | 861 | 856 | 177 | 179 | 241 | 179 |

| 185.60.112.157 - 1 | 857 | 851 | 177 | 178 | 241 | 179 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

This is to a retail Wow server. Drops are happening every 20-30 mins and last between 1 and 2 minutes.
Click to expand...
This doesn't seem to be on our network. Please escalate to your ISP as I'm seeing PL on the first hop from your router and through to the handover.
 
Last edited:
Kryptonite said:
MTR:
Start: Mon Feb 14 05:56:51 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.25.2 0.0% 10 0.9 0.9 0.6 1.9 0.0
3.|-- Blizzard 0.0% 10 1.0 1.0 0.8 1.2 0.0
4.|-- 137.221.66.32 0.0% 10 0.5 1.0 0.4 5.5 1.6
5.|-- 137.221.77.76 0.0% 10 7.5 23.0 7.4 155.0 46.4
6.|-- 137.221.65.35 0.0% 10 8.7 17.1 7.3 42.5 15.2
7.|-- 137.221.65.19 0.0% 10 7.5 7.5 7.4 7.6 0.0
8.|-- 137.221.79.34 0.0% 10 7.7 11.4 7.5 45.3 11.9
9.|-- 195.66.224.25 0.0% 10 8.1 8.1 8.0 8.2 0.0
10.|-- 197.148.66.42 0.0% 10 8.1 8.1 8.0 8.2 0.0
11.|-- 13-71-148-197.as37497.za.net 0.0% 10 150.9 150.9 150.8 151.0 0.0
12.|-- 161-68-148-197.as37497.za.net 0.0% 10 151.0 150.9 150.8 151.0 0.0
13.|-- 166-69-148-197.as37497.za.net 0.0% 10 151.0 150.9 150.8 151.0 0.0
14.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 150.9 150.9 150.8 151.0 0.0
15.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 186.7 166.9 153.3 211.0 19.6


14/02/2022 05:56:51 UTC
--------------------

MTR:
Start: Mon Feb 14 05:56:51 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.2 0.7 0.0
2.|-- 37.244.24.131 0.0% 10 0.8 1.0 0.6 3.2 0.7
3.|-- Blizzard 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.46 0.0% 10 3.3 3.4 0.5 17.5 5.6
5.|-- 137.221.78.52 0.0% 10 1.1 1.1 1.0 1.2 0.0
6.|-- 137.221.65.74 0.0% 10 1.1 3.2 1.0 21.0 6.2
7.|-- 137.221.78.32 0.0% 10 1.3 1.3 1.1 1.5 0.0
8.|-- 80.249.213.88 0.0% 10 7.5 7.4 7.2 7.8 0.0
9.|-- 13-71-148-197.as37497.za.net 0.0% 10 150.2 150.2 150.1 150.4 0.0
10.|-- 161-68-148-197.as37497.za.net 0.0% 10 150.3 150.2 150.1 150.4 0.0
11.|-- 166-69-148-197.as37497.za.net 0.0% 10 150.2 150.2 150.0 150.2 0.0
12.|-- core.cr-01.cp1.za.ws.net.za 0.0% 10 150.3 150.3 150.2 150.4 0.0
13.|-- as-vuma.cp-is-br-01.za.ws.net.za 0.0% 10 158.6 157.7 152.0 176.3 7.5

Here is the MTR, each time i test, it looks fine and because it's so intermittent, we never catch it but it's really bad.
Click to expand...
If you can keep an eye on it and let us know when it happens. Open a ticket if you can. As you mentioned above, these are clear here.
 
We're picking up on some packet loss on Blizzard services; seems to originate at the Blizzard peering point at LINX. We have escalated to the respective upstream to investigate and resolve.
 
websquadza said:
We're picking up on some packet loss on Blizzard services; seems to originate at the Blizzard peering point at LINX. We have escalated to the respective upstream to investigate and resolve.
Click to expand...
Thank you, it's just impossible to do it during the day as i work, and then in the evenings when you raid, it's near impossible to catch as when you experience it, by the time you get the tests back everything is ok.
 
websquadza said:
This doesn't seem to be on our network. Please escalate to your ISP as I'm seeing PL on the first hop from your router and through to the handover.
Click to expand...
Host%SentRecvBestAvrgWrstLast
192.168.0.104136413600700
160.119.237.12704134413401631
102.220.48.29041344134131353
160.119.232.161041344134131163
160.119.232.86141084101242511825
197.148.69.165140364010242616726
197.148.68.162140173986272913229
197.148.71.14140284000170171628171
197.148.66.41140354009170171308171
195.66.226.234140324005171176311173
137.221.79.3333698359302304856266
No response from host10083700000
137.221.65.775341932511772584823179
137.221.78.55140193989177179314178
185.60.112.157140173986177179315179

Did another extended test with 0 packet loss until hop 5. I see you have identified an issue with Blizzard services already though.
 
Blizzard is always an issue, but its an issue outside of WS, I just use ExitLag and don't have an issue anymore

1644834927922.png
 
Last edited:
S7wede said:
​
Host%SentRecvBestAvrgWrstLast
192.168.0.104136413600700
160.119.237.12704134413401631
102.220.48.29041344134131353
160.119.232.161041344134131163
160.119.232.86141084101242511825
197.148.69.165140364010242616726
197.148.68.162140173986272913229
197.148.71.14140284000170171628171
197.148.66.41140354009170171308171
195.66.226.234140324005171176311173
137.221.79.3333698359302304856266
No response from host10083700000
137.221.65.775341932511772584823179
137.221.78.55140193989177179314178
185.60.112.157140173986177179315179


Did another extended test with 0 packet loss until hop 5. I see you have identified an issue with Blizzard services already though.
Click to expand...
Kryptonite said:
Thank you, it's just impossible to do it during the day as i work, and then in the evenings when you raid, it's near impossible to catch as when you experience it, by the time you get the tests back everything is ok.
Click to expand...
We've re-routed some traffic and working with our vendor to resolve an issue here. In the meanwhile, you may experience slightly higher latencies but no packet loss while running over this path. We will get this back down to normal as soon as we can.
 
websquadza said:
We've re-routed some traffic and working with our vendor to resolve an issue here. In the meanwhile, you may experience slightly higher latencies but no packet loss while running over this path. We will get this back down to normal as soon as we can.
Click to expand...
meh, it's not great at all but let me know once it's resolved its fine.
 
I got to be honest, this is a bit frustrating. I don’t see other ISPs having this much downtime so regularly and it’s affecting my work.
 
@websquadza completely down again for the past 20 min. Agh this is really frustrating.

Will post an mtr of the downtime when my desktop comes back online.
 
Yeah also seeing this on multiple threads. @websquadza are most ISP'S Forced to use this KZN provider due to being the only provider or cost related, or is it simply by choice and chance that so many ISP'S use this provider?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X