Packet loss problem being ignored

Technical Support
A lot of people across the EU are having packet loss problems mean while we are being told it's all of our ISPs' fault. Packet loss problems cause inputs such reloading and shooting get ignored with a lot of high packet loss causing the inputs to be completely ignored server side. Death cams show that the player who killed you didn't even see you do the action, I have created a lot of threads with video evidence which has been completely ignored and Blizzard wont even address the issue, which shows bad customer service and has big red flags for the future of overwatch, especially if they plan to make it competitive in this state.

Videos show graphs of random packet loss, you can see that when I reload sometimes the animation starts and stops halfway through, when throwing a flash bang with mcree it shows the throwing animation and the particle effect but it doesn't explode leading to some incredibly frustrating moments.

even the movement of the bots is laggy:

https://www.youtube.com/watch?v=vzN9LuvrzOo GRAPH

https://www.youtube.com/watch?v=c-YO5qRWmPk WATCH LAST PART OF THE VIDEO WHERE I CONSTANTLY RELOAD AS 76.
Hello,

Please post at least 2 pathpings created while the game client is warning of packet loss. https://eu.battle.net/support/en/article/718
Tracing route to 185.60.112.157 over a maximum of 30 hops

0 Diesel.mshome.net [192.168.0.3]
1 * * *
Computing statistics for 0 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Diesel.mshome.net [192.168.0.3]

Trace complete.

==============================================================

Tracing route to 185.60.112.157 over a maximum of 30 hops

1 * * * Request timed out.
2 10 ms 14 ms 13 ms glfd-core-2a-xe-803-0.network.virginmedia.net [80.7.14.9]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 34 ms 39 ms 39 ms ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158]
9 215 ms 190 ms 47 ms 80.249.208.83
10 40 ms 41 ms 39 ms 37.244.10.35
11 41 ms 39 ms 39 ms 37.244.10.103
12 67 ms 213 ms 191 ms 185.60.112.157

Trace complete.
They possibly know about this, but it's the weekend. And bank holiday Monday too!
29/05/2016 17:26Posted by danpen
They possibly know about this, but it's the weekend. And bank holiday Monday too!

They knew this since the open beta and have failed to even acknowledge it which is starting concern a lot of people
here is a full explanation of the problem + a couple workarounds.
http://eu.battle.net/forums/en/overwatch/topic/17611871471#post-1
29/05/2016 17:31Posted by Diesel
They knew this since the open beta and have failed to even acknowledge it which is starting concern a lot of people

Packet loss is when some of your internet traffic is lost in transit. Blizzard has a bunch of servers in a few data centres around the world. Any problem which isn't server-side is something they can't control.

They don't own the internet. They don't control the backbone infrastructure in Europe. I asked for a pathping so I could see where the packet loss was occurring, but unfortunately your modem killed it.

If your internet traffic isn't reaching Blizzard's server with low latency and zero packet loss then that's one for your internet provider and their peering partners to talk about. Because they're the ones routing it.

Think of it like this - you send Blizzard internet traffic. Amazon sends you items you've purchased. Imagine your purchase got damaged in the delivery van and Amazon tried to blame you. They tried saying you were responsible for the condition of something before you received it. That argument not fair to you? Then it's not fair to Blizzard.
29/05/2016 17:51Posted by Doomie
29/05/2016 17:31Posted by Diesel
They knew this since the open beta and have failed to even acknowledge it which is starting concern a lot of people

Packet loss is when some of your internet traffic is lost in transit. Blizzard has a bunch of servers in a few data centres around the world. Any problem which isn't server-side is something they can't control.

They don't own the internet. They don't control the backbone infrastructure in Europe. I asked for a pathping so I could see where the packet loss was occurring, but unfortunately your modem killed it.

If your internet traffic isn't reaching Blizzard's server with low latency and zero packet loss then that's one for your internet provider and their peering partners to talk about. Because they're the ones routing it.

Think of it like this - you send Blizzard internet traffic. Amazon sends you items you've purchased. Imagine your purchase got damaged in the delivery van and Amazon tried to blame you. They tried saying you were responsible for the condition of something before you received it. That argument not fair to you? Then it's not fair to Blizzard.


The problem is clearly server side (which you said yourself; the thing blizzard can control), no way can you say a common issue people around the globe are having problems with is a client side issue, because the likely hood of multiple ISPs having the same issue with one server is slim and is more likely the one server is the one with the issues. Not to mention this problem ONLY occurs with Overwatch, but the same people can play on other fps games with no packet loss at all.
29/05/2016 18:12Posted by Diesel
The problem is clearly server side

I connect to the same servers you do. I experience no packet loss.

Packet loss also doesn't really make sense in the context of a server-side issue. The server drops packets to... what? It's hard to get lost on the way to your destination if you're already there.


29/05/2016 18:12Posted by Diesel
no way can you say a common issue people around the globe are having problems with is a client side issue, because the likely hood of multiple ISPs having the same issue with one server is slim

And this right here shows a common misunderstanding of networking - "it isn't me so it must be you." Your ISP does not have infrastructure in every country of the world. No ISP does. After your traffic leaves their network and maybe a peering partner of theirs it'll travel through the network of a tier 1 ISP. Tier 1 ISPs are the biggest of the big - there's fewer than 20 of them in their world and the scale of them is massive.

This is a common denominator. If a tier 1 ISP is having problems and your traffic goes through them, then you will have problems.

I see from your pathping you're a customer of Virgin Media. So am I; I live in the Republic of Ireland. Here's a pathping I created;

Tracing route to 185.60.112.157 over a maximum of 30 hops

0 Messana.home [192.168.0.221]
1 192.168.0.1
2 10.240.208.1
3 109.255.253.254
4 ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
5 ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
6 dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
7 ldn-bb3-link.telia.net [62.115.116.132]
8 adm-bb3-link.telia.net [62.115.143.187]
9 adm-b2-link.telia.net [62.115.141.57]
10 62.115.46.198
11 37.244.10.33
12 185.60.112.157

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Messana.home [192.168.0.221]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.240.208.1
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% 109.255.253.254
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb3-link.telia.net [62.115.116.132]
0/ 100 = 0% |
8 35ms 0/ 100 = 0% 0/ 100 = 0% adm-bb3-link.telia.net [62.115.143.187]
0/ 100 = 0% |
9 37ms 0/ 100 = 0% 0/ 100 = 0% adm-b2-link.telia.net [62.115.141.57]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% 62.115.46.198
0/ 100 = 0% |
11 35ms 0/ 100 = 0% 0/ 100 = 0% 37.244.10.33
0/ 100 = 0% |
12 35ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

Trace complete.

Two hops configured to filter non-essential traffic (e.g. pathpings), but zero packet loss and no latency spikes. If the problem is server-side then it looks like the servers (those inanimate objects...) are playing favourites.

I've seen dozens of people affected. Every single pathping which works shows that the person's internet traffic is passing through the network of Zayo Group, a tier 1 ISP. Zayo are currently routing everyone through the US for some reason, and internet traffic going to the wrong continent and back again is why it's having problems. By contrast, as seen by my pathping, I'm going through the tier 1 ISP TeliaSonera.

I've explained what I believe, why I believe it and provided diagnostic data to substantiate my argument. If you want to be serious about disagreeing with me I expect you to do likewise when responding.
Zayo confirmed an update by Blizzard to the routing table a couple of days ago, and while the engineer I spoke to could'nt directly comment on why he suggested possible maintence as the reason. He also advised that Blizzard are the ones responsible for updating the routing not them or your ISP.
29/05/2016 18:36Posted by Doomie
29/05/2016 18:12Posted by Diesel
The problem is clearly server side

I connect to the same servers you do. I experience no packet loss.

Packet loss also doesn't really make sense in the context of a server-side issue. The server drops packets to... what? It's hard to get lost on the way to your destination if you're already there.


29/05/2016 18:12Posted by Diesel
no way can you say a common issue people around the globe are having problems with is a client side issue, because the likely hood of multiple ISPs having the same issue with one server is slim

And this right here shows a common misunderstanding of networking - "it isn't me so it must be you." Your ISP does not have infrastructure in every country of the world. No ISP does. After your traffic leaves their network and maybe a peering partner of theirs it'll travel through the network of a tier 1 ISP. Tier 1 ISPs are the biggest of the big - there's fewer than 20 of them in their world and the scale of them is massive.

This is a common denominator. If a tier 1 ISP is having problems and your traffic goes through them, then you will have problems.

I see from your pathping you're a customer of Virgin Media. So am I; I live in the Republic of Ireland. Here's a pathping I created;

Tracing route to 185.60.112.157 over a maximum of 30 hops

0 Messana.home [192.168.0.221]
1 192.168.0.1
2 10.240.208.1
3 109.255.253.254
4 ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
5 ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
6 dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
7 ldn-bb3-link.telia.net [62.115.116.132]
8 adm-bb3-link.telia.net [62.115.143.187]
9 adm-b2-link.telia.net [62.115.141.57]
10 62.115.46.198
11 37.244.10.33
12 185.60.112.157

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Messana.home [192.168.0.221]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.240.208.1
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% 109.255.253.254
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb3-link.telia.net [62.115.116.132]
0/ 100 = 0% |
8 35ms 0/ 100 = 0% 0/ 100 = 0% adm-bb3-link.telia.net [62.115.143.187]
0/ 100 = 0% |
9 37ms 0/ 100 = 0% 0/ 100 = 0% adm-b2-link.telia.net [62.115.141.57]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% 62.115.46.198
0/ 100 = 0% |
11 35ms 0/ 100 = 0% 0/ 100 = 0% 37.244.10.33
0/ 100 = 0% |
12 35ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

Trace complete.

Two hops configured to filter non-essential traffic (e.g. pathpings), but zero packet loss and no latency spikes. If the problem is server-side then it looks like the servers (those inanimate objects...) are playing favourites.

I've seen dozens of people affected. Every single pathping which works shows that the person's internet traffic is passing through the network of Zayo Group, a tier 1 ISP. Zayo are currently routing everyone through the US for some reason, and internet traffic going to the wrong continent and back again is why it's having problems. By contrast, as seen by my pathping, I'm going through the tier 1 ISP TeliaSonera.

I've explained what I believe, why I believe it and provided diagnostic data to substantiate my argument. If you want to be serious about disagreeing with me I expect you to do likewise when responding.


Ok so if it's my problem, what is it? I gave you the path ping and like always it doesn't do anything and I gave you a trace.
bump
Could this possibly have anything to do with the possible disconnects for NL/BE users aswell?
I hear it's because EU servers have to ping to a US server and then back to EU which causes horrid RTT fluctuations which then causes the interpolation delay to sky rocket after a certain amount of time in a game, this causes stupid packet losses
31/05/2016 01:04Posted by Hydern
Could this possibly have anything to do with the possible disconnects for NL/BE users aswell?


I am UK and I have the same problem on Virgin Media. The issue is completely being ignored and shoved off towards an ISP problem.

I already made a ticket with all the hoops and loops one must jump through just to make a ticket, I did all the steps like a good boy scout and of course (surprise surprise) the issue still persisted so I made the ticket. This issue only started for me after open beta. During closed beta this was NOT an issue. But when they changed to the open beta servers this became a massive issue.

I am 100% sure this is a server issue. League of Legends had the same for some time in Europe until they finally sorted their servers out (they changed to different server providers or even brought it in-house or something).

This issue is far too wide spread to be ISP specific, it is a Blizzard issue and Blizzard needs to fix this. This is getting ridiculous.

Oh and the ticket response? Based on your tracert and pathping it is clearly an ISP issue.
Still have these issues. If i ping -t while not playing i have no Request Time-out's, but when i run the game and run ping -t i lose connection to the game server at one point and in the console i see "Request Timed Out"

halp, the game is unplayable for me rn
29/05/2016 18:36Posted by Doomie
29/05/2016 18:12Posted by Diesel
The problem is clearly server side

I connect to the same servers you do. I experience no packet loss.

Packet loss also doesn't really make sense in the context of a server-side issue. The server drops packets to... what? It's hard to get lost on the way to your destination if you're already there.


29/05/2016 18:12Posted by Diesel
no way can you say a common issue people around the globe are having problems with is a client side issue, because the likely hood of multiple ISPs having the same issue with one server is slim

And this right here shows a common misunderstanding of networking - "it isn't me so it must be you." Your ISP does not have infrastructure in every country of the world. No ISP does. After your traffic leaves their network and maybe a peering partner of theirs it'll travel through the network of a tier 1 ISP. Tier 1 ISPs are the biggest of the big - there's fewer than 20 of them in their world and the scale of them is massive.

This is a common denominator. If a tier 1 ISP is having problems and your traffic goes through them, then you will have problems.

I see from your pathping you're a customer of Virgin Media. So am I; I live in the Republic of Ireland. Here's a pathping I created;

Tracing route to 185.60.112.157 over a maximum of 30 hops

0 Messana.home [192.168.0.221]
1 192.168.0.1
2 10.240.208.1
3 109.255.253.254
4 ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
5 ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
6 dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
7 ldn-bb3-link.telia.net [62.115.116.132]
8 adm-bb3-link.telia.net [62.115.143.187]
9 adm-b2-link.telia.net [62.115.141.57]
10 62.115.46.198
11 37.244.10.33
12 185.60.112.157

Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Messana.home [192.168.0.221]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.240.208.1
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% 109.255.253.254
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ra3-ae31-0.aorta.net [84.116.238.38]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% ie-dub01a-ri1-ae50-0.aorta.net [84.116.130.97]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% dbln-t2core-a-ae-0-0.aorta.net [213.46.165.2]
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb3-link.telia.net [62.115.116.132]
0/ 100 = 0% |
8 35ms 0/ 100 = 0% 0/ 100 = 0% adm-bb3-link.telia.net [62.115.143.187]
0/ 100 = 0% |
9 37ms 0/ 100 = 0% 0/ 100 = 0% adm-b2-link.telia.net [62.115.141.57]
0/ 100 = 0% |
10 37ms 0/ 100 = 0% 0/ 100 = 0% 62.115.46.198
0/ 100 = 0% |
11 35ms 0/ 100 = 0% 0/ 100 = 0% 37.244.10.33
0/ 100 = 0% |
12 35ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

Trace complete.

Two hops configured to filter non-essential traffic (e.g. pathpings), but zero packet loss and no latency spikes. If the problem is server-side then it looks like the servers (those inanimate objects...) are playing favourites.

I've seen dozens of people affected. Every single pathping which works shows that the person's internet traffic is passing through the network of Zayo Group, a tier 1 ISP. Zayo are currently routing everyone through the US for some reason, and internet traffic going to the wrong continent and back again is why it's having problems. By contrast, as seen by my pathping, I'm going through the tier 1 ISP TeliaSonera.

I've explained what I believe, why I believe it and provided diagnostic data to substantiate my argument. If you want to be serious about disagreeing with me I expect you to do likewise when responding.


Not quite sure i understood all of it, so i'll be straightforward, even if it makes me look naive : I am too customer of Virgin Media, in the Republic of Ireland. I had a couple of isolated and short episode of rubber banding, but to be honest i would rate my experience as flawless until a couple of days. Since last Monday, i rubber band like crazy, it became unplayable.

If i follow you, but again, i might just misunderstand this ISP/router gibberish, the problem is on my end... We have the same ISP, at least 20% chance to be both Dubliners, my experience was fine until now, but I or Virgin Media (or a Partner of them) did a surprise mess up that do not impact you ? I honestly don't get it...
I have the same problem with excessive packetloss.
My pathping is look like:

Pathping:
Routenverfolgung zu "185.60.112.157" ber maximal 30 Hops

0 Computername.RouterSpecifications [xxx.xxx.xxx.xxx]
1 Routertype.ip [xxx.xxx.xxx.xxx]
2 xxx.xxx.xxx.xxx
3 87.186.193.206
4 d-sb4-i.D.DE.NET.DTAG.DE [62.154.43.73]
5 f-sb1-i.F.DE.NET.DTAG.DE [217.5.92.42]
6 217.239.39.26
7 80.157.202.34
8 37.244.12.33
9 24.105.31.28
10 185.60.112.157

Berechnung der Statistiken dauert ca. 250 Sekunden...
Quelle zum Abs. Knoten/Verbindung
Abs. Zeit Verl./Ges.= % Verl./Ges.= % Adresse
0 Computername.RouterSpecifications [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Routertype.ip [xxx.xxx.xxx.xxx]
0/ 100 = 0% |
2 18ms 0/ 100 = 0% 0/ 100 = 0% xxx.xxx.xxx.xxx
0/ 100 = 0% |
3 18ms 0/ 100 = 0% 0/ 100 = 0% 87.186.193.206
0/ 100 = 0% |
4 25ms 0/ 100 = 0% 0/ 100 = 0% d-sb4-i.D.DE.NET.DTAG.DE [62.154.43.73]
0/ 100 = 0% |
5 28ms 0/ 100 = 0% 0/ 100 = 0% f-sb1-i.F.DE.NET.DTAG.DE [217.5.92.42]
0/ 100 = 0% |
6 23ms 0/ 100 = 0% 0/ 100 = 0% 217.239.39.26
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 80.157.202.34
0/ 100 = 0% |
8 23ms 0/ 100 = 0% 0/ 100 = 0% 37.244.12.33
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% 24.105.31.28
0/ 100 = 0% |
10 28ms 0/ 100 = 0% 0/ 100 = 0% 185.60.112.157

Ablaufverfolgung beendet.

Tracert:
Routenverfolgung zu 185.60.112.157 ber maximal 30 Hops

1 <1 ms <1 ms <1 ms Routername.ip [xxx.xxx.xxx.xxx]
2 19 ms 18 ms 18 ms xxx.xxx.xxx.xxx
3 18 ms 18 ms 18 ms 87.186.193.206
4 26 ms 24 ms 23 ms d-sb4-i.D.DE.NET.DTAG.DE [62.154.43.73]
5 24 ms 23 ms 24 ms f-sb1-i.F.DE.NET.DTAG.DE [217.5.92.42]
6 23 ms 23 ms 23 ms 217.239.39.26
7 23 ms 24 ms 23 ms 80.157.202.34
8 29 ms 29 ms 29 ms 37.244.12.33
9 30 ms 29 ms 30 ms 24.105.31.28
10 28 ms 29 ms 28 ms 185.60.112.157

Ablaufverfolgung beendet.

The data is without any spikes or something like that, but ingame i get both issue icons over and over and over and over.

This issue includes problems with shooting, hitboxes and affects attacking / defending skills priority.
Virgin media customer also experiencing this. The packet loss icon has been floating since I bought the game, yet in the last week its become a real issue effecting game play. Update and/or solutions would be great.
I can play YouTube and Call Of Duty Black Ops 3 at the same time and I still don't recieve quality drops on youtube or lag on B03. Sky customer and I get packet loss and the lightning bolt loop (I think that means poor connection to server) on every game I play. If packet loss is on my side, why can I play BO3 and YouTube at the same time? Both of which require bandwith? (Also, I have no idea what a pathping is or how to show you mine)

Join the Conversation

Return to Forum