Started the same for Azjol - Looks like whoever they peer with in the netherlands is having issues
Ran the same traceroute using PingPlotter Pro
share . pingplotter . com/eGAjWjk8CTW.png
Pings are fine when the data leaves my router + my ISPâs routers.
Soon as they hit ae1-br01-eqld5 . as57976 . net the lag begins.
That hostname resolves to 137.221.79.33 which when put into a ip whois is a Blizzard Entertainment IP situated in NL.
1 Like
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| dsldevice.lan - 0 | 21 | 21 | 2 | 9 | 31 | 11 |
| 172.16.16.94 - 0 | 21 | 21 | 10 | 14 | 33 | 13 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| 136.hiper04.sheff.dial.plus.net.uk - 0 | 21 | 21 | 12 | 15 | 33 | 14 |
| core1-BE1.southbank.ukcore.bt.net - 0 | 21 | 21 | 12 | 16 | 33 | 15 |
|core1-hu0-18-0-0.southbank.ukcore.bt.net - 0 | 21 | 21 | 17 | 20 | 33 | 17 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| ae1-br01-eqld5.as57976.net - 0 | 21 | 21 | 172 | 182 | 265 | 173 |
| xe-0-0-0-1-br01-eqny8.as57976.net - 0 | 21 | 21 | 175 | 186 | 223 | 218 |
| et-0-0-29-br02-eqny8.as57976.net - 0 | 15 | 15 | 172 | 743 | 4603 | 172 |
| et-0-0-3-br01-eqdc2.as57976.net - 0 | 21 | 21 | 171 | 186 | 235 | 176 |
| 137.221.65.148 - 0 | 21 | 21 | 173 | 184 | 223 | 176 |
| xe-0-0-0-0-br01-eqpa4.as57976.net - 0 | 21 | 21 | 176 | 186 | 231 | 180 |
| et-0-0-29-br02-eqpa4.as57976.net - 0 | 21 | 21 | 175 | 186 | 236 | 176 |
| et-0-0-3-br02-eqam1.as57976.net - 0 | 21 | 21 | 93 | 103 | 139 | 98 |
| 137.221.78.87 - 0 | 21 | 21 | 175 | 184 | 221 | 179 |
| 185.60.112.157 - 0 | 21 | 21 | 174 | 182 | 221 | 176 |
|________________________________________________|______|______|______|______|______|______|
ISP: Plusnet
Itâs happening to many people at once, I have never had any lag problems for years on this ISP (Sky) and the same time I get high ms, everyone else is saying the same, so itâs not us.
Currently playing on Sporregar, Sky is my ISP.
Definitely looks like there is a problem, too many of us from UK having 100+ MS today.
I personally sit at 20-30ms normally.
Blizzard please look into this!
Same issue, everything outside of the game is completely fine. WoW however is a completely different story.
Solid 158ms (world and home) in-game with noticeable input lag
Emerald Dream EU
BT ISP (UK)
Same issue on Outland EU!
Same on Azjol
So every single UK player Iâve spoken to has 180 ms, and only in WoW.
Yep, no issue here boys.
4 Likes
Honestly the frequency with which this patch has brought latency issues is completely unacceptable. IDK what the hell has happened to completely screw this patch but the amount of lag I deal with on a regular basis is just insane for such a huge company.
1 Like
Yeah even the Twitter Support gave an Overwatch player a generic response when they complained.
Itâs affecting all Blizzard games.
I know mate, itâs a tired refrain, always goes
- Not us guys! Must be you! Post a trace anyways!
- Twitter post : We are looking into an issue affected xyz
- Oh yeah it is actually us
- Fixed now!
3 Likes
Multi billion dollar company btw.
Tenner a month well spent!
Honestly itâs kinda sad how accurate this is.
1 Like
Interesting to see that some of you have horrible connections at your ISP level as well as the common issue we are seeing with Blizzard peering in the Netherlands 
I wonder how many hours time the player base loses waiting for a resolution whilst we wait for Blizzardâs internal politics to resolve who actually needs to pick this up. I can imagine all the service desk tickets getting closed and reassigned in circular loops right now.
I ran a pingplotter pro (Paid Tracerouting software) scan and the pings were totally fine at my routers and my ISPâs routers.
Soon as I hit Blizzardâs IP the pings went into the 100âs.
Virgin Media in particular will have slightly higher ping times due to how DOCSIS technology works but 104+ ms is certainly not normal to a server thats not even that far from me (450 miles or so)
Other games hosted in the Netherlands such as League of Legends EUW are giving me pings of 25-27
1 Like
Well it could very well be BT lines doing something to upset things between Blizzard, it happened plenty of times before, and Blizzard canât actually see it from their end because itâs not actually their fault⌠So donât blame them. Seems thatâs what happening again
Same problem here in the UK. Glad I am not alone on this issue at least.
I usually have 21ms but I have 160+ right now.
My ISP is Vodafone.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| vodafone.broadband - 36 | 113 | 73 | 0 | 0 | 1 | 0 |
| 84.65.64.1 - 43 | 101 | 58 | 3 | 3 | 6 | 4 |
| 63.130.104.198 - 43 | 101 | 58 | 3 | 4 | 6 | 4 |
| lonap-ix.blizzardonline.net - 44 | 99 | 56 | 4 | 10 | 83 | 6 |
| ae1-br01-eqld5.as57976.net - 43 | 101 | 58 | 165 | 168 | 248 | 166 |
| xe-0-0-0-1-br01-eqny8.as57976.net - 44 | 99 | 56 | 165 | 169 | 217 | 172 |
| et-0-0-29-br02-eqny8.as57976.net - 13 | 183 | 161 | 165 | 168 | 230 | 180 |
| et-0-0-3-br01-eqdc2.as57976.net - 45 | 98 | 54 | 165 | 169 | 225 | 166 |
| 137.221.65.148 - 0 | 271 | 271 | 165 | 168 | 284 | 167 |
| xe-0-0-0-0-br01-eqpa4.as57976.net - 43 | 101 | 58 | 165 | 173 | 276 | 166 |
| et-0-0-29-br02-eqpa4.as57976.net - 46 | 97 | 53 | 165 | 167 | 193 | 166 |
| et-0-0-3-br02-eqam1.as57976.net - 2 | 255 | 251 | 88 | 92 | 207 | 89 |
| 137.221.78.89 - 43 | 101 | 58 | 165 | 167 | 224 | 166 |
| 137.221.66.47 - 40 | 105 | 63 | 165 | 166 | 169 | 166 |
| 185.60.112.157 - 43 | 101 | 58 | 165 | 165 | 170 | 167 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.243 ms 0.241 ms 0.240 ms
2 37.244.24.131 (37.244.24.131) 0.435 ms 0.526 ms 0.625 ms
3 Blizzard Blizzard 1.090 ms 1.110 ms 1.153 ms
4 137.221.66.46 (137.221.66.46) 0.984 ms 0.988 ms 0.988 ms
5 137.221.78.88 (137.221.78.88) 161.685 ms 161.704 ms 161.707 ms
6 137.221.65.92 (137.221.65.92) 161.476 ms 161.642 ms 161.632 ms
7 137.221.65.34 (137.221.65.34) 161.762 ms 162.052 ms 162.029 ms
8 137.221.65.16 (137.221.65.16) 161.959 ms 161.976 ms 161.963 ms
9 137.221.65.149 (137.221.65.149) 161.803 ms 161.731 ms 161.711 ms
10 137.221.65.15 (137.221.65.15) 161.582 ms 161.590 ms 161.698 ms
11 137.221.65.102 (137.221.65.102) 161.584 ms 161.549 ms 161.495 ms
12 137.221.65.25 (137.221.65.25) 161.593 ms 161.668 ms 161.504 ms
13 137.221.79.32 (137.221.79.32) 161.726 ms 161.726 ms 161.725 ms
14 * * *
15 * * *
08/03/2020 19:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 4.036 ms 4.037 ms 4.039 ms
2 37.244.24.131 (37.244.24.131) 4.646 ms 4.671 ms 4.677 ms
3 Blizzard Blizzard 4.878 ms 4.957 ms 5.021 ms
4 137.221.66.46 (137.221.66.46) 4.671 ms 4.675 ms 4.681 ms
5 137.221.78.88 (137.221.78.88) 165.581 ms 165.585 ms 165.595 ms
6 137.221.65.92 (137.221.65.92) 165.512 ms 161.750 ms 161.770 ms
7 137.221.65.34 (137.221.65.34) 161.915 ms 161.581 ms 161.570 ms
8 137.221.65.16 (137.221.65.16) 161.732 ms 161.746 ms 161.747 ms
9 137.221.65.149 (137.221.65.149) 161.595 ms 161.684 ms 161.675 ms
10 137.221.65.15 (137.221.65.15) 161.545 ms 170.241 ms 169.461 ms
11 137.221.65.102 (137.221.65.102) 173.664 ms 172.885 ms 172.374 ms
12 137.221.65.25 (137.221.65.25) 161.613 ms 161.703 ms 161.678 ms
13 137.221.79.32 (137.221.79.32) 161.630 ms 161.889 ms 162.238 ms
14 * * *
15 * * *
08/03/2020 19:52:45 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3006ms
08/03/2020 19:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.278 ms 0.280 ms 0.284 ms
2 37.244.24.131 (37.244.24.131) 0.550 ms 0.641 ms 0.738 ms
3 Blizzard Blizzard 2.831 ms 2.851 ms 2.857 ms
4 137.221.66.46 (137.221.66.46) 1.017 ms 1.033 ms 1.035 ms
5 137.221.78.88 (137.221.78.88) 161.765 ms 161.786 ms 161.781 ms
6 137.221.65.92 (137.221.65.92) 225.652 ms 223.124 ms 223.098 ms
7 137.221.65.34 (137.221.65.34) 161.661 ms 161.701 ms 161.687 ms
8 137.221.65.16 (137.221.65.16) 161.842 ms 161.860 ms 161.863 ms
9 137.221.65.149 (137.221.65.149) 161.689 ms 161.655 ms 161.645 ms
10 137.221.65.15 (137.221.65.15) 161.718 ms 161.714 ms 161.701 ms
11 137.221.65.102 (137.221.65.102) 161.537 ms 161.660 ms 161.518 ms
12 137.221.65.25 (137.221.65.25) 161.639 ms 161.648 ms 161.756 ms
13 137.221.79.32 (137.221.79.32) 161.569 ms 161.584 ms 161.577 ms
14 * * *
15 * * *
08/03/2020 19:52:48 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2998ms
08/03/2020 19:52:45 UTC
--------------------
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.335 ms 1.239 ms 1.254 ms
2 37.244.25.130 (37.244.25.130) 1.254 ms 1.255 ms 1.254 ms
3 Blizzard Blizzard 1.343 ms 1.392 ms 1.434 ms
4 137.221.66.36 (137.221.66.36) 0.965 ms 1.042 ms 2.446 ms
5 137.221.77.68 (137.221.77.68) 152.748 ms 152.765 ms 152.766 ms
6 137.221.65.16 (137.221.65.16) 152.582 ms 152.904 ms 152.844 ms
7 137.221.65.149 (137.221.65.149) 152.748 ms 152.777 ms 152.778 ms
8 137.221.65.15 (137.221.65.15) 152.761 ms 152.737 ms 152.725 ms
9 137.221.65.102 (137.221.65.102) 153.232 ms 153.210 ms 152.681 ms
10 137.221.65.25 (137.221.65.25) 154.081 ms 152.654 ms 152.722 ms
11 137.221.79.32 (137.221.79.32) 153.163 ms 152.807 ms 152.932 ms
12 * * *
13 * * *
14 * * *
15 * * *
08/03/2020 19:52:50 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3009ms
08/03/2020 19:52:50 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
08/03/2020 19:52:53 UTC
--------------------
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.288 ms 0.281 ms 0.282 ms
2 37.244.25.130 (37.244.25.130) 0.505 ms 0.754 ms 0.770 ms
3 Blizzard Blizzard 1.416 ms 1.431 ms 1.468 ms
4 137.221.66.36 (137.221.66.36) 0.895 ms 0.965 ms 1.010 ms
5 137.221.77.68 (137.221.77.68) 152.983 ms 152.983 ms 152.985 ms
6 137.221.65.16 (137.221.65.16) 152.946 ms 152.913 ms 152.896 ms
7 137.221.65.149 (137.221.65.149) 152.726 ms 153.068 ms 153.052 ms
8 137.221.65.15 (137.221.65.15) 153.044 ms 153.041 ms 153.039 ms
9 137.221.65.102 (137.221.65.102) 153.037 ms 152.761 ms 152.747 ms
10 137.221.65.25 (137.221.65.25) 152.777 ms 152.490 ms 152.938 ms
11 137.221.79.32 (137.221.79.32) 154.519 ms 153.683 ms 152.772 ms
12 * * *
13 * * *
14 * * *
15 * * *
08/03/2020 19:52:58 UTC
--------------------
MTR:
Start: Sun Mar 8 19:52:45 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.24.131 0.0% 10 0.4 0.6 0.4 1.6 0.3
3.|-- Blizzard 0.0% 10 1.1 2.8 1.0 15.6 4.5
4.|-- 137.221.66.46 0.0% 10 0.7 0.7 0.5 1.6 0.0
5.|-- 137.221.78.88 0.0% 10 161.8 163.0 161.5 175.7 4.4
6.|-- 137.221.65.92 0.0% 10 161.6 165.6 161.6 196.5 10.9
7.|-- 137.221.65.34 0.0% 10 161.6 161.7 161.5 162.4 0.0
8.|-- 137.221.65.16 0.0% 10 161.7 162.1 161.5 166.4 1.5
9.|-- 137.221.65.149 0.0% 10 162.2 161.8 161.5 162.6 0.0
10.|-- 137.221.65.15 0.0% 10 161.7 167.8 161.6 210.6 15.5
11.|-- 137.221.65.102 0.0% 10 161.7 161.7 161.6 162.1 0.0
12.|-- 137.221.65.25 0.0% 10 183.9 163.9 161.6 183.9 7.0
13.|-- 137.221.79.32 0.0% 10 161.7 174.9 161.6 245.1 28.1
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:52:45 UTC
--------------------
MTR:
Start: Sun Mar 8 19:52:45 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.24.131 0.0% 10 0.5 0.6 0.4 1.1 0.0
3.|-- Blizzard 0.0% 10 1.0 1.1 1.0 1.2 0.0
4.|-- 137.221.66.46 0.0% 10 0.8 3.7 0.6 30.6 9.5
5.|-- 137.221.78.88 0.0% 10 161.6 166.6 161.6 210.6 15.4
6.|-- 137.221.65.92 0.0% 10 161.7 167.4 161.6 181.2 8.1
7.|-- 137.221.65.34 0.0% 10 161.6 165.4 161.5 198.8 11.7
8.|-- 137.221.65.16 0.0% 10 161.6 161.7 161.5 162.9 0.0
9.|-- 137.221.65.149 0.0% 10 161.6 161.6 161.6 161.8 0.0
10.|-- 137.221.65.15 0.0% 10 161.7 161.8 161.5 162.3 0.0
11.|-- 137.221.65.102 0.0% 10 163.6 167.2 161.6 201.1 12.6
12.|-- 137.221.65.25 0.0% 10 161.6 167.2 161.6 205.6 14.0
13.|-- 137.221.79.32 0.0% 10 161.8 163.3 161.7 177.2 4.9
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:52:45 UTC
--------------------
MTR:
Start: Sun Mar 8 19:52:48 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.2 0.2 0.3 0.0
2.|-- 37.244.24.131 0.0% 10 0.5 0.9 0.4 2.1 0.3
3.|-- Blizzard 0.0% 10 2.3 1.3 1.0 2.3 0.5
4.|-- 137.221.66.46 0.0% 10 0.7 0.7 0.5 0.8 0.0
5.|-- 137.221.78.88 0.0% 10 161.6 164.2 161.5 187.9 8.3
6.|-- 137.221.65.92 0.0% 10 161.6 162.1 161.6 166.4 1.4
7.|-- 137.221.65.34 0.0% 10 161.7 165.9 161.5 203.9 13.4
8.|-- 137.221.65.16 0.0% 10 161.6 161.7 161.5 161.9 0.0
9.|-- 137.221.65.149 0.0% 10 161.7 161.6 161.5 161.7 0.0
10.|-- 137.221.65.15 0.0% 10 161.6 161.7 161.6 161.8 0.0
11.|-- 137.221.65.102 0.0% 10 161.7 163.6 161.5 181.3 6.2
12.|-- 137.221.65.25 0.0% 10 161.6 162.4 161.5 169.1 2.2
13.|-- 137.221.79.32 0.0% 10 161.7 169.4 161.7 222.9 19.3
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:52:48 UTC
--------------------
TRACEROUTE:
traceroute to 84.65.93.114 (84.65.93.114), 15 hops max, 60 byte packets
1 Blizzard Blizzard 20.905 ms 20.883 ms 20.881 ms
2 37.244.25.130 (37.244.25.130) 20.883 ms 20.886 ms 20.888 ms
3 Blizzard Blizzard 20.823 ms 20.828 ms 20.830 ms
4 137.221.66.36 (137.221.66.36) 20.760 ms 20.790 ms 20.794 ms
5 137.221.77.68 (137.221.77.68) 162.797 ms 162.799 ms 162.802 ms
6 137.221.65.16 (137.221.65.16) 162.774 ms 158.751 ms 158.754 ms
7 137.221.65.149 (137.221.65.149) 158.429 ms 158.443 ms 158.444 ms
8 137.221.65.15 (137.221.65.15) 158.211 ms 152.955 ms 152.937 ms
9 137.221.65.102 (137.221.65.102) 162.114 ms 161.362 ms 161.325 ms
10 137.221.65.25 (137.221.65.25) 159.849 ms 155.404 ms 154.588 ms
11 137.221.79.32 (137.221.79.32) 154.561 ms 153.743 ms 152.732 ms
12 * * *
13 * * *
14 * * *
15 * * *
08/03/2020 19:53:01 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 2999ms
08/03/2020 19:53:01 UTC
--------------------
MTR:
Start: Sun Mar 8 19:52:50 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.6 0.2 1.3 0.0
2.|-- 37.244.25.130 0.0% 10 0.6 0.7 0.4 1.5 0.0
3.|-- Blizzard 0.0% 10 2.3 1.6 1.2 2.3 0.0
4.|-- 137.221.66.36 0.0% 10 0.9 2.2 0.8 11.9 3.4
5.|-- 137.221.77.68 0.0% 10 153.5 153.4 152.5 157.7 1.5
6.|-- 137.221.65.16 0.0% 10 152.6 152.6 152.5 152.9 0.0
7.|-- 137.221.65.149 0.0% 10 152.8 154.0 152.5 166.5 4.4
8.|-- 137.221.65.15 0.0% 10 164.8 155.1 152.5 164.8 4.9
9.|-- 137.221.65.102 0.0% 10 163.8 155.2 152.5 166.6 5.3
10.|-- 137.221.65.25 0.0% 10 163.0 154.2 152.5 163.0 3.3
11.|-- 137.221.79.32 0.0% 10 158.4 153.8 152.7 158.4 1.8
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:52:50 UTC
--------------------
PING:
PING 84.65.93.114 (84.65.93.114) 56(84) bytes of data.
--- 84.65.93.114 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3002ms
08/03/2020 19:53:04 UTC
--------------------
MTR:
Start: Sun Mar 8 19:52:56 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 1.2 0.0
2.|-- 37.244.25.130 0.0% 10 6.7 1.4 0.5 6.7 1.9
3.|-- Blizzard 0.0% 10 1.5 2.5 1.2 11.9 3.3
4.|-- 137.221.66.36 0.0% 10 1.2 1.2 1.0 2.0 0.0
5.|-- 137.221.77.68 0.0% 10 180.5 157.7 152.5 180.5 8.9
6.|-- 137.221.65.16 0.0% 10 152.7 155.2 152.5 170.2 5.8
7.|-- 137.221.65.149 0.0% 10 152.7 153.4 152.6 157.0 1.6
8.|-- 137.221.65.15 0.0% 10 152.7 154.1 152.6 166.4 4.3
9.|-- 137.221.65.102 0.0% 10 152.5 162.5 152.5 248.5 30.2
10.|-- 137.221.65.25 0.0% 10 153.2 153.1 152.6 154.0 0.0
11.|-- 137.221.79.32 0.0% 10 201.1 159.1 152.8 201.1 15.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:52:56 UTC
--------------------
MTR:
Start: Sun Mar 8 19:53:01 2020 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.2 0.6 0.0
2.|-- 37.244.25.130 0.0% 10 0.6 1.6 0.5 10.2 3.0
3.|-- Blizzard 0.0% 10 1.3 1.8 1.0 6.4 1.5
4.|-- 137.221.66.36 0.0% 10 0.9 2.3 0.8 9.5 2.8
5.|-- 137.221.77.68 0.0% 10 152.6 153.6 152.5 159.0 1.9
6.|-- 137.221.65.16 0.0% 10 158.8 155.3 152.5 173.0 6.5
7.|-- 137.221.65.149 0.0% 10 152.6 157.2 152.6 198.2 14.4
8.|-- 137.221.65.15 0.0% 10 152.8 153.0 152.6 154.6 0.3
9.|-- 137.221.65.102 0.0% 10 152.7 155.2 152.5 178.3 8.1
10.|-- 137.221.65.25 0.0% 10 152.6 153.2 152.5 156.0 0.8
11.|-- 137.221.79.32 0.0% 10 191.5 158.5 152.8 191.5 12.7
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
08/03/2020 19:53:01 UTC
--------------------
08/03/2020 19:53:01 UTC
--------------------Itâs not your ISP itâs Blizzard.
I am with Virgin Media, a company who runs their network privately so to say that my ISP is having the same issues as people on BT, Sky, Plusnet, Vodafone (ISPâs who use the BT infrastructure) is a sign the issue at blizzardâs end.