Hello,
i had some serious disconnects from the servers in the past days. Its not on my side, i simply lose the connection to the battle.net servers. While ingame you see the game running, my characters moves in a certain direction and after a fes seconds the game disconnects. I had this a few times in the past weeks.
Today i saw the exact same disconnect at a streamer living in my region, using the same isp. It was in a ranked game and can be seen on twitch @ 02H 01M. There were 4 players disconnected at the same time.
I lost the connection on my client too, so this is a complete regional disconnect to the blizzard servers.
Would you be able to run this winMTR test for 15-20 minutes while the issue is happening? This will help pinpoint where the data is being lost in route to our servers. Be sure to use the in-game IP address using Netgraph (CTRL+SHIFT+N) for the “host” in the winMTR tool.
Please put the results in a quote box. It should look like this when it’s posted.
Looks like the problem starts here and gets progressively worse after that. This node is owned by “Deutsche Telekom AG” - Reaching out to them to resolve the issue would be the best solution.
It may be possible to bypass this by using a VPN but that is not something we can support doing since that involves a third party service. Even then it would only be a way around the problem not a fix. Even if you do try this I do still highly recommend contacting the ISP.
OP is describing the very same thing that is happening to me. It’s not us. It might be our provider not connecting to the Blizzard servers, which could be a problem from both sides or only Blizzard itself.
Exactly the same thing happened to me at least 5 or 6 times in 4 days. In order to log back on, I need to reboot my computer or else Battle net doesn’t want to start. It reads “the service is busy” if I try to log back on right after the disconnect.
It’s really annoying and makes me want to quit competitive (right when I thought about playing back in comp).
Maybe it’s time Blizzard took responsibility for issues that are on their end… It’s impossible that all internet providers from different countries in the whole EU areas have the same issue at the same time.
Something’s wrong and it’s definitely on Blizzard’s end since we didn’t have those crash bugs before. A lot of people from my contact list encountered the same issue (Germany, Israel, Switzerland, Latvia etc…).
Please let Blizzard know something is wrong with the servers.
Same happened to me many times the past few days. Only today i had the same type of dc from the blizzard client like 4 times. it takes minutes for me to get back into the lobby, i even lose my ultcharge after reconnecting. by the time i need to reconnect the enemy team already pushed through the whole map. its super frustrating and it takes away the fun that competetive overwatch offers. i hope it gets fixed soon. otherwise i might just quit the game since there is no point in playing a competetive game wich disconnects you out of nowhere multiple times a day. every other application that requires a stable internet connection is working just fine. the disconnect happens exclusively to the blizzard server. i play overwatch for over 2 years and never had this type of disconnects before.
Not to start an argument here, but that is not how WinMTR works. With the winMTR test, you have to start with the highest up node having issues. In this case, the problem appears to be with the peering before it hits our peer network, which means we don’t have control over it.
If you’re referring to this from the “Wrst” column
This hop de-prioritizes test packets. In either case, with the information we have, we can’t provide more help. Do you have a different winMTR test which doesn’t show problems at this hop which also had a disconnection issue? If so you can post that and we can look for problems further down.
We’ve identified the original player’s problem. If you’d like help for your own issue, please start your own thread and include a winMTR test. There are no current server issues causing this problem, so you’ll need to catch the disconnection live and provide the information so we can look for more options.
To prevent this thread from getting out of hand, we’re not going to be troubleshooting everybody’s individual issue.
I linked this thread to a new post in the eu forums as a reference. There are multiple reports of this issue from all over europe. This is NOT related to my side or the side of my isp.
This customer support doesn’t even know how to read these data. This WinMTR actually shows the hosts with the worst connection. And this is “et-0-0-2-br01-eqpa4.as57976 net”.
A simple Whois and the owner is found: Blizzard Entertainment. A very small amount of loss is normal on ICMP cause routers skip those pakets in favour for real data.
Even the host before the bad one is owned by Blizzard (ae1-br01-eqfr5.as57976 net). Can there be a better connection to your servers as linked direct from my isp to your servers? These are 5 hops (excluding my own router) before reaching the final server.
There a better tools to visualize a traceroute to the destination. Using these clearly shows that the Blizzard hops are passing out from time to time causing the disconnects.
Due to the fact that no other services cancel the connection its an issue on your side.
Pretty much. Because most of the people I know (from Europe) experience the exact same thing, so it’s not an individual issue per player than it’s something to do with Blizzard’s servers or a connection to European players. Making tons of threads for the same issue seems a bit excessive, because it’s all the same problem.
just dropping in to say that this issue has been happening for weeks (shortly before the Storm Rising update) and it is definitely an issue on Blizzards or rather BattleNets end. It is very concerting that no bluepost has taken responsibility for this yet and rather blames ISPs or faulty user connections.
This has been happening multiple times for weeks, and it is always the same kind of connections that get signed out of BattleNet at the SAME time. Stop trying to put the blame on us or an ISP.
Sorry for the harsh words, but it has gotten very concerting that nothing has been done to fix this sofar.
As explained above, this hop does not respond to test packets, which inflates the value for the “worst ping.” If the number were a real value for the hop, you wouldn’t be able to connect at all. In other words, this hop’s value for worst ping should not be used as a means of troubleshooting.
My last comment on this, because it becomes a farce now: There are no “test packets”. A not responding host would be a loss or not answering.
When i trace down packets over the internet the protocol “icmp” is used, which is part of tcp/ip or this case simply IPv4. WinMTR is no tool exclusively used by Blizzard and the networking rules doesn’t change for Blizzard. How to correctly read a WinMTR table can be found easily on google.
Quote: “[…] In this instance you’ll need to escalate the issue to the first hop showing the issue. For example, if the hop belongs to your ISP, they will need to be advised - however if it’s further on (a carrier or on the Neural network) then you will need to advise us (comment: In this case Blizzard) via our support channels.”
This is a new table generated today. The first node showing the issue is “et-0-0-2-br01-eqpa4.as57976 net”. This node has the ip adress “137 221 65 26”. This host is running in the netherlands. This host is operated by Blizzard. Whois Infos can be found simply on google.
In addtion, the next worse peak value of 150ms on “ae1-br01-eqfr5.as57976 net” is also on your side.
At this point you see that the average latencies are totally fine which represent the normal working hops. There are a few parts where these “worst” values are coming from. 3500ms latency is a 3,5 second lag to your server/hop. 3,5 seconds are ages in this peering networks and is enough to disconnect services.
There is even an email adress for blizzard peering services showing up, maybe you cantact your own dudes and link them to here that they can check it…
You seem to be confusing latency with packet loss, and misunderstanding how ICMP echo requests work. The false latency numbers you see there are not causing your disconnections. The packet loss you linked earlier is the likely cause. As a DDoS mitigation measure, some of the equinix hops later in the test will ignore some ICMP echo requests, which these tests (tracert/pathping/winMTR) use. If these hops were legitimately having problems, we would have mass disconnections and our queues would be inundated with reports, which is not the case (we have telemetry on our end which watches for this kind of thing.)
You’ve been given the information we can give you on this issue. If you’d like to continue working with us on this issue, you’ll need to escalate the packet loss that I pointed out to you to your ISP. We will not assist with this as it is not our ISP. You can also just use a VPN to work around the problem.
Beyond this there is nothing else we can do for you. Good luck whatever you choose to do from here.
But if they acknowledge it’s all the same problem they have to acknowledge that it’s THEIR issue instead of blindly blaming the router/isp/moon phase and washing their hands of it.
Drakuloth, not that I expect a direct response, but your info, I went and checked the same directions exi linked. I also brought this scenario to one of the heads of my business technologies department. They gave pretty much the exact same answer and info exi suggests.
So let’s see. Same issue occurs with only Overwatch and no other online game. it affects multiple different ISPs who have nothing to do with each other. The Data is showing that it’s happening on Blizzard’s side. Experts in the field confirm. You say it’s the ISP’s fault.
Look, I get that you guys probably don’t have an exact idea what’s happening. Trouble shooting is a labyrinthine process and I can’t even begin to guess why only Overwatch is the only software affects. But could you guys at least acknowledge the issue and say you’re working but don’t have an ETA? That type of transparency goes a LOT further than blame shifting and avoidance.
The last week this is happening to me as well. Today I played at least 30 minutes match, very close and we take the last point in overtime for a draw having 30 seconds for possible win for taking the second point. Guess what happens? Battlenet disconnects, I get kicked out, cant reconnect in time and I actually get a lose and a suspension for leaving the game not mentioning the huge lose of rating I got literally because your problem. That certainly feels very good, everything else about my connection was fine. Thanks