But why is there a traffic jam at 3am? I can understand during prime time, but not late at night. Another question. I had traffic jam related issues with my ISP a few years back, during prime time, couldn’t play any games cause it would just spike, but the thing is, it always spiked. No matter what, the entire game was up and down, up and down. Start at 26, spike to 150, go down for a few seconds, spike up, spike down, nothing like what’s happening now.
Why does it spike in some HotS games I play and not others? How can I be in a 25 min game, where my ping doesn’t go below 150 (showing an OCE server with ctrl alt f), then the moment game ends, I requeue, and in under 5 mins I’m in a new game and my ping doesn’t go over 30? How did the traffic clear in that small amount of time but not the 25 min game? It isn’t a case of like, oh it just happened to disappear in that time. It’s a case of. The moment I get in the game, I’ll see myself go up to 150, play the 20 mins, play another, see I go to 25, stay there the entire game, play another, see myself go up to 150 and stay there.
This is for HotS and not OW. I’d ask in the HotS forums but here gets more responses.
Edit: On a good note, not a single bad game all night, 8 games, so thats nice.
I thought my issue was resolved on the weekend but first chance to play this week and it’s back. I appear to be getting correctly matched to the SYD servers repeatedly but the lag issue has returned (170 - 300+ ms)
I Winmtr’d the server details from the server that it occurred on.
Is that still correct? i.e. 37.244.10.1 details at start of thread
Looking at this your routing is running through Telia which is a European ISP!!! also EQAM1 sounds alot like Equinix AM1 which is an Equinix data centre in Amsterdam!!! i swear these issues are caused by the new IP ranges we connect to for SYD2 are IP addresses registered in the netherlands. Blizz needs to just give us back Amazon Web Servers atleast those kinda worked.
Tonight’s games have been heavily affected. Strange thing is my ping has never gone over 100ms and for the most part and approx 60% of the match is playable. The other 40% is a rubberbanding mess.
This match was creeping up to 70ms and then would return to 40ish. The match prior stayed within the 40ish range the entire time however rubber banding still occurred halfway through the match with a massive spike that stopped the game dead in its tracks but did not kick me.
Usual data
ISP iinet
Australia
8-9pm AEST
All matched played in QP mode
If you have this mechanic where it detects a high ping on a local server and so it goes to a distant server, that’s a silly mechanic. Going to a distant server guarantees a bad gaming experience. Being on a local server with a bad temporary connection is still temporary. So the better idea is to go to the local server ALWAYS.
So implement a Force Local Server option. This would put you to the local server (or the server of your choice) no matter the ping. THEN we can judge what the real problem is. As it is now, your method of selecting a server based on the ping here and now, regardless of location obfuscates the issue, making it difficult to get to the root cause of the problem.
they won’t do it. apparently not enough people to care about this situation xd… my isp reset everything from their end for me and everything. nothing helped. Blizzard also said theyve been in contact with my isp which is a lie. considering i’ve asked. My isp said they have their priority set to low.
Haven’t had any issues (like the ones we have all been experiencing) since the Summer games update… fingers crossed it’s back to normal now - for me at least!
Its obvious what Overwatch did, read the patch notes for the summer event. They did some server optimization and tracking in the patch, they obviously messed up the server route optimization. So even though you select NA server, it thinks for what ever reason you should be on the SA server, and nothing you do is going to change that. So your ISP routes you to that server which gives you insane lag and cuts you off of LFG. Bliz needs to at least acknowledge that this is their problem and that they are working on it. Because right now the only thing I have seen them say about it is “we think its a traffic jam with your ISP”. If your network/server team truly thinks that then fire them all, I can do much better by myself.
Hi All, Just checking in to see if anyone else has been having any more issues or have Blizzard done some policy based routing changes on their Equinox network equipment.
Not saying the issue is resolved, just that I haven’t had it happen to me since then - although I’m definitely not playing as much as I’m getting some fps issues.
Have tried a few quick play matches early this week and I have played around 5 or so competitive matches tonight and have had no issues with either incorrect server or latency issues. All matches I have been placed into syd2 server and pings have been stable normally around 35ish and with 50ms at worst. Not a great deal of testing but hopefully resolved. Will report any further issues but wont be until the weekend that I get to play again. Thanks
My ping has come down from 50ms to about 47ms but im getting constant packet loss in game though no packet loss in my WinMTR I could be wrong but I notice that I have quite a few spikes where my ping sometimes triples once it reaches telstraglobal/overwatch servers and Im wondering if my game client is sometimes processing 2 ticks as I often feel like im missing animations. It is most noticeable in the scenario where you land in a junkrat trap+mine as sometimes ill see the trap animation and go straight to the kill cam and sometimes ill just see the mine animation. another example is quite often i can still jump when in a junkrat trap. Im beginning to feel like my ping is TOO average i.e. i dont have the benefits of low latency but also dont have the benefits of high latency (by benefits im talking about the favour the shooter model) one thing i notice alot when playing on the 140ms servers (pse1) I seem to survive taking damage longer and have less WTF moments.
When I was connecting to the pse2 server I didn’t have any troubles, and I’m no longer connecting to pse1 which is good. However, the syd2 server is giving me ridiculous amounts of packet loss and frequent lag spikes sometimes every 30 seconds or so. Usually sit around 35ms, but i’ve been regularly going up to 50-60, and often spiking up to 150+ Not sure why we can’t go back to being on pse2, but here’s my WinMTR for that host.
