Look at this recent WinMTR 16% & 17% packet loss this only happens on Blizzard servers nothing else. I will also open a ticket with my ISP. But I really don’t think this is there fault.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
| 192.168.1.1 - 0 |
904 |
904 |
0 |
0 |
6 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| 133.hiper04.sheff.dial.plus net uk - 98 |
184 |
4 |
18 |
18 |
21 |
18 |
| 132.hiper04.sheff.dial.plus net uk - 0 |
904 |
904 |
18 |
19 |
35 |
20 |
| 195.99.125.140 - 0 |
904 |
904 |
17 |
18 |
29 |
18 |
| peer2-et-7-0-1.slough.ukcore bt net - 0 |
903 |
903 |
19 |
20 |
64 |
19 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| ae1-br01-eqld5.as57976 net - 17 |
545 |
455 |
24 |
26 |
112 |
24 |
| et-0-0-2-br02-eqam1.as57976 net - 16 |
561 |
475 |
25 |
33 |
132 |
30 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| No response from host - 100 |
181 |
0 |
0 |
0 |
0 |
0 |
| ________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderPreformatted text
It could be neither of them, could be some word DNS settings or something like that. Hopefully the staff have some answers for you!
Yea, hopefully. I have opened a support ticket with my ISP (Plusnet). So hopefully this issue gets resolved.
This is DEFINITELY on Blizzard’s behalf. Spikes happen only in Overwatch and they started happening ONLY after the Winter Wonderland update for me. And if you scroll down the subforum you’ll see 10’s more having the exact same issue. Not to mention providing those tracer routes and all that with almost none of them getting a responce at all. Those spikes render the game unplayable at all, And for 6+ months now there has been no definitive answer on Blizzard’s support about what is done or should be done about it.
1 Like
Is there anyone from Blizzard who has any input? Contacted my ISP and they’re pointing the finger firmly at Blizzard servers!
1 Like
Tracing route to 5.42.169.174 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 3 ms 4 ms 10.33.221.58
3 7 ms 7 ms 7 ms sto7.dr1.a3network se [88.129.174.30]
4 7 ms 7 ms 7 ms sto1.dr3.a3network se [88.129.128.112]
5 6 ms 6 ms 6 ms sto1.cr2.a3network se [88.129.128.166]
6 6 ms 6 ms 6 ms sto1.br1.a3network se [85.8.9.8]
7 7 ms 6 ms 7 ms as57976-10g-sk1.sthix net [192.121.80.100]
8 25 ms 21 ms 22 ms ae1-br01-eqsk1.as57976 net [137.221.86.33]
9 30 ms 24 ms 24 ms et-0-0-3-br01-eqam1.as57976 net [137.221.65.110]
10 * * * Request timed out.
11 * * * Request timed out.
ISP have confirmed that every thing on their side is fine.
Looking at the forums recently I’m not the only one having problems, what’s going on Blizzard?
Good morning crzyfool,
Your issue seems to start when you enter your ISPs network. There is 98% data loss recorded which seems to be the reason for your issue.
Kind regards
What’s your opinion?
Is that not just because it stops responding to ping requests?
Hello again,
No, it won’t stop responding. It either can’t be pinged and that is when you get 100% data loss (which isn’t bad in that case because the server just can’t be pinged) or you get 0% when there is no issue. Anything between 0 and 100 % is bad and causes issues.
Kind regards
What’s your opinion?
Thanks for the quick reply. I will pas this onto my ISP and update this thread for future reference.
Looking at some of the other posts in this forum surely this is a Blizzard issue?
Good morning,
In order to check this, please provide the requested information here.
We would need:
Details of issue :
Date/time you first experienced the issue :
City and country :
ISP :
Trace Route (created whilst experiencing issue) : battle.net/support/article/performing-a-traceroute
MTR Report (created whilst experiencing issue) : Blizzard Support - Running WinMTR
Details of issue : As stated above ping spike of up to 4000 - 5000 ms
Date/time you first experienced the issue : Started around the end of May
City and country : UK, Northern Ireland
ISP : Plusnet
Trace Route (created whilst experiencing issue) :
Tracing route to 5.42.173.169 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 17 ms 17 ms gi12-0-0-441.ptn-ag04.plus.net [84.93.253.72]
3 18 ms 18 ms 18 ms gi2-1-444.ptn-gw01.plus.net [84.93.253.79]
4 18 ms 18 ms 18 ms 195.99.125.140
5 18 ms 18 ms 18 ms peer1-et-0-0-1.interxion.ukcore.bt.net [62.172.103.54]
6 * * * Request timed out.
7 25 ms 25 ms 25 ms ae1-br01-eqld5.as57976.net [137.221.79.33]
8 28 ms 32 ms 32 ms et-0-0-2-br02-eqam1.as57976.net [137.221.65.91]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
MTR Report (created whilst experiencing issue) :
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 3718 | 3718 | 0 | 0 | 3 | 0 |
| gi12-0-0-441.ptn-ag04.plus.net - 0 | 3717 | 3717 | 17 | 17 | 75 | 25 |
| gi2-1-444.ptn-gw01.plus.net - 0 | 3717 | 3717 | 17 | 18 | 59 | 18 |
| 195.99.125.140 - 0 | 3717 | 3717 | 17 | 18 | 60 | 18 |
| peer1-et-0-0-1.interxion.ukcore.bt.net - 0 | 3717 | 3717 | 18 | 19 | 60 | 19 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| ae1-br01-eqld5.as57976.net - 0 | 3715 | 3715 | 24 | 33 | 1939 | 25 |
| et-0-0-2-br02-eqam1.as57976.net - 1 | 3597 | 3579 | 24 | 60 | 4597 | 29 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 745 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
Hmm, 8 days and no reply from Blizzard.
1 Like
Can anyone from Blizzard comment? I’ve posted results where the hops from my ISP are fine but, Blizzard servers are still suffering from ping spikes and packet loss.
Same issue plusnet as well. I even found your post on plusnet’s forum…
Blizzard won’t even let me submit ticket. Problem started since early September for me. No idea what is going on but the end result is game being so unplayable. Fps drop to oblivion, before I was 130 -200 on fights on high settings and now I get constant fps drops and even on low doesn’t help much. Ping in game seems supposedly normal but varies a tiny bit unlike before, but I think is bs and actually is inconsistent. Hammond is literally failing 10-20% grapples, and I cannot generate speed on lucio from wallriding because of this.
Issues happen on ow since Sept. Either the halloween patch broke game or sth wrong with that hop.
1 Like
Me and my friends have had insane lag spikes 1-2 times a day (game freezes, red flashing icon and sometimes we even disconnect from the game). It was happening since 3 weeks ago, and this problem has occurred on 3 separate ISPs.
It is an issue with one of the nodes that Blizzard owns to route us from UK to their game servers on the continent. But they refuse to acknowledge that. Try to launch game to US servers and you will see high, but stable ping with no rubber band, packet loss or other networking issues. Im from UK too and struggle with the et-0-0-2-br02-eqam1.as57976 net node which spikes, just like yours, to north of 4000ms which causes packet loss, rubber band and stuttering.
1 Like