Random Ping Spikes on NA Central (ORD1) Server

Technical Support
Prev 1 2 3 5 Next
I'm having these issues as well.

Verizon Fios with Gigabit. Normally I'm 20-30ms. Past couple days randomly spike to 80-100ms for a few seconds. Happens pretty frequently.

Also East coast. Connected to ord1 last I had this issue but it might be showing up on multiple servers. That's just what I saw when I thought to check.


I'm on US East with Fios as well (150/150). This has been happening since about late Jan every time I'm connected to any ord1 server. My normal ping is 24-28ms and it'll spike to 80-100ms for a few seconds (sometimes a lot longer).

I noticed I was connected to an lax server the other night and even though my ping was 73-74ms, it never spiked the entire night.
This is also happening on Google fiber as well
side note.. I changed my region to Europe... I get a solid 70 ping there, no fluctuations lol...

I ping lower to EU then I do to my own country...
02/11/2018 03:36 PMPosted by strych9
side note.. I changed my region to Europe... I get a solid 70 ping there, no fluctuations lol...

I ping lower to EU then I do to my own country...

After reading your post I decided to change my server to Asia, since I'm on the West Coast, and the game ran better connecting to that server than it does to lax1 right now. My ping and RTT(around 120 each) were of course higher but it was steady and I wasn't rubber banding every 10-20 seconds.

What a joke.
Let's see how long it takes them to acknowledge this, and what they say.

02/11/2018 06:07 PMPosted by Drakuloth
Hey there, you two.

Servers are currently stable and have been for a while now. I see there's been a large amount of speculation on some threads you've both been involved in. However, we aren't currently aware of any widespread issues with latency, especially ones that have been ongoing for several weeks. Every once in a while a single large scale ISP issue will pop up that affects thousands of users, but those are also usually handled within 24 hours. Currently we aren't tracking any of those, so we need to figure out what's going on here.

The vast majority of the time when we hear issues like yours, there's something local that you can fix or that needs your ISP's intervention. If there is something going on, we can grab some information to see if we can find it, though.

Can you get us a [url="https://battle.net/support/article/27780"]WinMTR test[/url] while the problems are actively happening and let us know what IP address you see in the top left of the netgraph? It's possible you're being routed to the wrong server, or it's equally likely that the problem is just the route you take to our servers.

Thanks!


Wow. I almost thought this time it might not go this way...

He's focused on it being a server issue too. It can be a path issue, but that doesn't mean they just excuse themselves and do nothing about it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

02/11/2018 06:33 PMPosted by Drakuloth
That is certainly your prerogative, but until we get those tests, we can't help. If you decide to get us the data we need to assist, I'll be happy to give it a look for you. Until then there's nothing we can do for you. Good luck.


I've done this before with them and it sucks having to go through it but they really do need the help apparently. More help than they should need, granted, but we might just have to suck it up and start jumping through some hoops. Start with WinMTRs if you're on at peak time and go from there.

https://us.battle.net/forums/en/overwatch/topic/20757255749

The last post here has instructions.

By the way, this is starting to spread on this forum now.
Same thing happens for me

My ping is normally 80ms and 95 RTT, every 10 seconds it spikes to 100ms and 160 RTT. Will provide a video if Blizz wants to check.

I play other blizzard games like SC2 and Diablo 3 on the east coast server located on chicago and its all good.
It's definitely not a client side issue. When everyone in every single one of my games complains and is saying the same thing.... something is wrong.

I don't think this is a routing issue either, that would effect some and leave others perfectly fine.

I've gone as far and kicking every other device off my network. Pinging Google's servers at a constant ~20ms while I watch my latency in Overwatch from from 20>90>20>90>20>90>20 multiple times a minute.
All night last night it put me on lax1 100 ping but not fluctuating. This past week it's normally 45 ping with intermittent spikes up to 200 then back to 45.
Hey folks, we're investigating these reports.

If you're able to post the results of a WinMTR test while the problems are actively happening and let us know what IP address you see in the top left of the netgraph (ctrl-shift-N on PC)?
02/12/2018 08:04 AMPosted by Bill Warnecke
Hey folks, we're investigating these reports.

If you're able to post the results of a [url="https://battle.net/support/article/27780"]WinMTR test[/url] while the problems are actively happening and let us know what IP address you see in the top left of the netgraph (ctrl-shift-N on PC)?

I put a few here Bill with the 2 i.p address I saw. ( looks like I missed a few numbers on one I'll update it when I get home)I'll try to get more info tonight and put it up tomorrow.

Also do you want all info put into this thread so I know where to put it so I know you will see it.

https://us.battle.net/forums/en/overwatch/topic/20752580207#post-11
I have posted on several threads that I am also having the ping spike problem. It is only during peak times and has been happening since the Verizon issue forced blizzard to reroute internet traffic. Blizzard please try to fix this. Everyone on this forum supports your game. I can only speak for myself when I say OW is my favorite game of all time and I’m an old dude that’s been around since Atari 2600 was the peak of gaming. OW rules! But this ping issue is really putting a damper on my enthusiasm. We would appreciate any help you could give us with this. Thank you in advance.
Just want to add in counter-strike servers using AWS in montreal (specifically 3rd party server owners) are also giving me ping spikes. Does OW use AWS? Or maybe something is going on along the route
So I think the problem might just be the game is sending people to the wrong servers. Last night I was playing fine on the “laxl” server with my normal 30PNG&40RTT(I’m west coast so that makes sense) but the game would sometimes put me in “ord” server and I’d get the 150-1000RTT spikes. I would just leave and que again until I got a west coast server(sometimes it would take a while). This is all in arcade so I didn’t care about leaving but I could see if you’re playing comp and it puts you in a server you aren’t supposed to be in you can’t just leave...
02/11/2018 06:16 AMPosted by strych9
as soon as the round starts though and a fight occurs, you can watch the ping fluctuate all over.

At night time though? Forget about it - it goes from 40 to 150 and sometimes 200 - extremely unreliable.

This. I called my internet company about it. (Central US).
TECH showed up today!
There is nothing wrong with my house. They said there is signal issue with the lines. (recent lag anyway)
He said there's going to be maintenance done to fix my issue within the next day or so. (line maintenance of some sort...?)
The RTT spikes in Overwatch were why I called anyway.
Server numbers were 24.105.4*.**(*) *=any number it seems.
02/12/2018 12:36 PMPosted by Audaylon
02/11/2018 06:16 AMPosted by strych9
as soon as the round starts though and a fight occurs, you can watch the ping fluctuate all over.

At night time though? Forget about it - it goes from 40 to 150 and sometimes 200 - extremely unreliable.

This. I called my internet company about it. (Central US).
TECH showed up today!
There is nothing wrong with my house. They said there is signal issue with the lines. (recent lag anyway)
He said there's going to be maintenance done to fix my issue within the next day or so. (line maintenance of some sort...?)
The RTT spikes in Overwatch were why I called anyway.
Server numbers were 24.105.4*.**(*) *=any number it seems.


I work for the cable company. While you may have additional issues related to a line issue(it's not that uncommon) this is not the issue many people are having.
I made 100% sure it was not on my end before coming to the forums and running diagnostics on the server end of things.

I'm no network engineer but It seems like it's a issue with the ORD1 server or a hop to it.
02/12/2018 01:29 PMPosted by Strife
I made 100% sure it was not on my end before coming to the forums and running diagnostics on the server end of things.
I try to make sure of this too. But hearing that it's a line issue isn't comforting at all. How long will my line issue last? We'll find out.
02/12/2018 01:29 PMPosted by Strife
this is not the issue many people are having.

The high RTT spikes during the game in which doesn't show up on the WinMTR test?
Those problems right?
I've had these issues the past couple of weeks. Practice range is awful. In game it comes and goes.

I talked to Blizzard CS last night, provided the WinMTR report to them. Showed 2% packet loss on my end. Which I don't doubt. However, I do think something is going on where players aren't connecting to the right server or something like that. I don't have issues with other games. Just Overwatch. It's almost like someone else said, we are randomly connecting to the wrong server, like I get one halfway around the world and get 300 ping.

Blizzard you have my tests, screenshots and much more info already from my convo with one of your reps. (they were awesome btw).
02/12/2018 01:36 PMPosted by Audaylon
02/12/2018 01:29 PMPosted by Strife
I made 100% sure it was not on my end before coming to the forums and running diagnostics on the server end of things.
I try to make sure of this too. But hearing that it's a line issue isn't comforting at all. How long will my line issue last? We'll find out.
02/12/2018 01:29 PMPosted by Strife
this is not the issue many people are having.

The high RTT spikes during the game in which doesn't show up on the WinMTR test?
Those problems right?


Yes. I don't know about you local cable companies policys but the company I work for we have a 48 business hour rule. That means the line tech has to look into the issue within that amount of time, generally it's same day. If it's a intermittent snr issue they can take time to locate. If it's low forword signals out of the tap that's same day repair most the time.
Typically if it's a snr issue that's reflected in slows speeds. So if your speeds and ping are normal using a testing site while your seeing the ping spikes in overwatch it's unrelated to your line issue.
02/12/2018 08:04 AMPosted by Bill Warnecke
Hey folks, we're investigating these reports.

If you're able to post the results of a [url="https://battle.net/support/article/27780"]WinMTR test[/url] while the problems are actively happening and let us know what IP address you see in the top left of the netgraph (ctrl-shift-N on PC)?


Here are the results of my test

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 10.0.0.1 - 0 | 108 | 108 | 4 | 13 | 20 | 17 |
| 96.120.12.141 - 0 | 108 | 108 | 11 | 14 | 67 | 15 |
|ae-104-rur202.littleton.co.denver.comcast.net - 0 | 108 | 108 | 12 | 16 | 69 | 18 |
|ae-2-rur201.littleton.co.denver.comcast.net - 0 | 108 | 108 | 12 | 16 | 69 | 18 |
| ae-18-ar01.denver.co.denver.comcast.net - 0 | 108 | 108 | 11 | 21 | 142 | 14 |
|be-33652-cr02.1601milehigh.co.ibone.comcast.net - 0 | 108 | 108 | 12 | 16 | 70 | 14 |
|be-11721-cr02.denver.co.ibone.comcast.net - 0 | 108 | 108 | 12 | 16 | 70 | 19 |
|be-10517-cr02.350ecermak.il.ibone.comcast.net - 0 | 108 | 108 | 35 | 39 | 93 | 35 |
|be-10563-pe01.350ecermak.il.ibone.comcast.net - 0 | 108 | 108 | 35 | 38 | 92 | 36 |
|173-167-56-238-static.hfc.comcastbusiness.net - 0 | 108 | 108 | 34 | 37 | 92 | 36 |
| ae1-br01-eqch2.blizzardonline.net - 0 | 108 | 108 | 34 | 39 | 92 | 40 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 21 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider


The IP address was 24.105.44.65:26561
Here is what you asked for.

1. Here is a youtube link (copy/paste) https://youtu.be/cw5GeGG0Qqg of WinMTR/Actual in-game/speed test stats (typically my up/down is 900/900) - skip to the 2 minute mark to view this in-action. What you will see is the game start at 150 ping, work its way down to 40, then climb right back up to 150 - this goes on over and over and over. Keep in mind, prior to this issue, my 'normal' ping was about 20-30 max. At this point, i'd be happy if I had to live with 40 forever. But 150-200? :/

2. Here are the WinMTR stats -

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 183 | 183 | 0 | 0 | 2 | 0 |
| 216.239.169.3 - 0 | 183 | 183 | 0 | 1 | 4 | 1 |
| 216.239.161.253 - 0 | 183 | 183 | 1 | 1 | 6 | 2 |
| sbb.eth-1-1.mlx4b - 0 | 183 | 183 | 1 | 2 | 14 | 2 |
| 205.204.28.202 - 0 | 183 | 183 | 5 | 6 | 20 | 6 |
| lag-112.ear3.Miami2.Level3.net - 1 | 180 | 179 | 6 | 8 | 360 | 6 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear2.Miami1.Level3.net - 0 | 183 | 183 | 6 | 7 | 17 | 7 |
| ae1-br01-eqmi2.blizzardonline.net - 0 | 183 | 183 | 6 | 7 | 51 | 7 |
|xe-0-0-36-1-br01-eqda6.blizzardonline.net - 0 | 183 | 183 | 34 | 35 | 55 | 43 |
| et-0-0-49-br01-eqch2.blizzardonline.net - 0 | 183 | 183 | 38 | 39 | 52 | 39 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 37 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Join the Conversation

Return to Forum