As many (many) others have been saying, I too am experiencing the constantly fluctuating ping and rubber banding / lag issues. It’s happens every 2-3 comp games and my ping will go from 70 to 200+ with multi-second delays on many occasions. This is clearly something to do with connecting to the OW server specifically, as all other games, connection tests, and applications work flawlessly on a 500mB fiber connection simultaneously.
This makes comp basically unplayable and causes a loss for me and my team whenever it occurs.
@prometheus which ISP provider are you using? I’m on Wave Brodband (Bay Area CA) and having the EXACT issue…started happening 2-3 days ago. Basically 2-3 games in and then the rubber banding happens consistently making it impossible to play.
Heya, also just started having this issue again today after a few days of excellent performance after it had apparently been fixed. Wave Broadband in California. Seems every few games, I get a game with wildly fluctuating pings, from 60-200, and major constant orange bars in the net graph. I’ll grab an MTR later tonight probably.
Edit: I shouldn’t say every few games. It’s been two so far, but both in the last hour. Really sad to see this back again. I’d try to contact my ISP about it, but last time I waited for 45 minutes for an agent before giving up.
Yeah, I’m posting the update here instead of calling the ISP because I already know the techs there aren’t likely to be able to do anything. Plus Blizz already has seen and remedied the issue once so it looks like they may need to continue that same effort.
I have the same issue in Seattle right now. I called Wave and they said they cannot see any issues on their end, or issues with my building.
I’m concluding that this is 100% blizzard server issues – because I have a room mate on the same exact connection that plays overwatch. We have had separate games today where I will have terrible ping for an entire comp match while my room mate has completely fine ping in their game. This has been going on all day today for a handful of games between our computers. I’ve a little upsetting because I’ve had uncontrollable losing streaks for no reason.
I can also confirm that this is just overwatch and not any other software/device.
The WAVE packet loss issue has returned for us as well. I am from the WAVE CALIFORNIA thread:
Our thread was CLOSED a few days back when WAVE apparently fixed the issue related to exchange points as told by Blizzard CS. The issue was in fact resolved for us for me personally about 4 days solid with zero Inbound packet loss or lat spikes.
TODAY all of a sudden the problem manifests again the same way as described.
I have informed CS by reopening my ticket and also asked for the other support thread to be reopened so others can chime in.
You guys seem to have started posting in here also starting today voiceing your issues returning. No coincidence. Just an FYI.
I ADVISE ALL TO OPEN A SUPPORT TICKET so Blizz gets some good volume coming in.
+1, reappeared tonight for me. Attached below is LookingGlass info at time of error. Didn’t get to fire up WinMTR for the problematic game.
Do want to point out that this coincides with the recent OW patches (Bastet). As pointed out in the previous thread on this topic (Wave Broadband California Packet Loss - Nov 22 2018), this seems to coincide with OW client changes.
Did anyone try PTR within this same time period? Were connection issues present there as well?
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.289 ms 0.281 ms 0.280 ms Blizzard(24.105.18.2) 0.617 ms 0.664 ms 0.718 ms
3 137.221.105.14 (137.221.105.14) 0.955 ms 0.967 ms 0.980 ms
4 137.221.66.18 (137.221.66.18) 0.940 ms 0.941 ms 0.940 ms
5 137.221.83.66 (137.221.83.66) 12.963 ms 12.970 ms 12.970 ms
6 137.221.65.68 (137.221.65.68) 12.763 ms 12.818 ms 12.799 ms
7 137.221.65.1 (137.221.65.1) 12.787 ms 12.895 ms 12.880 ms
8 137.221.65.7 (137.221.65.7) 12.871 ms 12.779 ms 12.749 ms
9 137.221.70.32 (137.221.70.32) 12.670 ms 12.676 ms 12.668 ms
10 cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182) 13.029 ms 12.615 ms 12.911 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404.net (192.175.28.239) 36.449 ms 35.899 ms 35.030 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404.net (174.127.141.70) 34.993 ms 34.508 ms 34.350 ms
13 cr1-sea-be100-4000.bb.as54858.net (216.243.28.206) 34.290 ms 33.837 ms 33.806 ms
14 HEINEBOREL 34.101 ms 34.109 ms 34.157 ms
10/01/2019 07:51:32 UTC
--------------------
TRACEROUTE:
traceroute to HEINEBOREL, 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.500 ms 1.499 ms 1.499 ms Blizzard(24.105.18.2) 2.242 ms 2.271 ms 2.275 ms
3 137.221.105.14 (137.221.105.14) 2.286 ms 2.333 ms 2.335 ms
4 137.221.66.18 (137.221.66.18) 2.261 ms 2.282 ms 2.301 ms
5 137.221.83.66 (137.221.83.66) 13.887 ms 13.904 ms 13.907 ms
6 137.221.65.68 (137.221.65.68) 13.754 ms 13.237 ms 13.212 ms
7 137.221.65.1 (137.221.65.1) 13.159 ms 13.094 ms 13.091 ms
8 137.221.65.7 (137.221.65.7) 13.066 ms 13.359 ms 13.313 ms
9 137.221.70.32 (137.221.70.32) 12.838 ms 12.830 ms 12.824 ms
10 cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182) 13.030 ms 12.904 ms 13.147 ms
11 cr1-pdx-a-hu-0-7-0-1.bb.as11404.net (192.175.28.239) 33.665 ms 34.123 ms 33.317 ms
12 cr2-sea-a-hu-0-7-0-6.bb.as11404.net (174.127.141.70) 32.887 ms 32.896 ms 33.121 ms
13 cr1-sea-be100-4000.bb.as54858.net (216.243.28.206) 33.375 ms 33.022 ms 33.015 ms
14 HEINEBOREL 34.096 ms 34.113 ms 34.405 ms
10/01/2019 07:51:33 UTC
--------------------
MTR:
Start: Thu Jan 10 07:51:33 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.3 0.0 Blizzard 0.0% 10 0.5 2.3 0.5 18.0 5.5
3.|-- 137.221.105.14 0.0% 10 0.7 0.7 0.5 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.66 0.0% 10 13.0 13.4 12.8 17.9 1.5
6.|-- 137.221.65.68 0.0% 10 12.9 13.7 12.8 16.6 1.1
7.|-- 137.221.65.1 0.0% 10 13.0 14.5 12.8 25.5 4.0
8.|-- 137.221.65.7 0.0% 10 12.9 15.3 12.8 32.8 6.3
9.|-- 137.221.70.32 0.0% 10 12.7 15.5 12.6 28.4 5.7
10.|-- cr1-sjo-p200.bb.spectrumnet.us 0.0% 10 13.7 12.9 12.7 13.7 0.0
11.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404.net 0.0% 10 33.3 33.3 33.2 33.4 0.0
12.|-- cr2-sea-a-hu-0-7-0-6.bb.as11404.net 0.0% 10 32.7 32.9 32.7 33.2 0.0
13.|-- cr1-sea-be100-4000.bb.as54858.net 0.0% 10 33.3 33.2 32.9 33.4 0.0
14.|-- HEINEBOREL 0.0% 10 35.2 34.6 34.2 35.2 0.0
10/01/2019 07:51:33 UTC
--------------------
MTR:
Start: Thu Jan 10 07:51:33 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.6 2.3 0.5 18.0 5.5
3.|-- 137.221.105.14 0.0% 10 0.7 0.7 0.5 0.8 0.0
4.|-- 137.221.66.18 0.0% 10 0.7 0.7 0.5 0.8 0.0
5.|-- 137.221.83.66 0.0% 10 13.0 13.3 12.8 17.7 1.3
6.|-- 137.221.65.68 0.0% 10 12.9 13.6 12.7 16.6 1.2
7.|-- 137.221.65.1 0.0% 10 12.9 14.4 12.8 25.6 4.0
8.|-- 137.221.65.7 0.0% 10 12.8 15.3 12.7 32.8 6.3
9.|-- 137.221.70.32 0.0% 10 12.6 15.0 12.6 24.1 4.4
10.|-- cr1-sjo-p200.bb.spectrumnet.us 0.0% 10 18.3 13.4 12.7 18.3 1.7
11.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404.net 0.0% 10 33.3 33.3 33.2 33.4 0.0
12.|-- cr2-sea-a-hu-0-7-0-6.bb.as11404.net 0.0% 10 32.7 32.9 32.7 33.2 0.0
13.|-- cr1-sea-be100-4000.bb.as54858.net 0.0% 10 33.3 33.2 32.9 33.4 0.0
14.|-- HEINEBOREL 0.0% 10 34.8 34.5 34.0 34.9 0.0
10/01/2019 07:51:32 UTC
--------------------
Additionally, I suspect what Blizz is doing on their end is merging our MTR / LookingGlass routes and looking for the common problematic hops. Please post (anonymized) connection info if y’all got them!
Post this here since my issue seems directly related to whatever is going on with Wave. Until today I've had no issues since the last set of fixes went in:
On Fibersphere in Portland too. The issue seems sporadic for me. Every other game. However when the fixes for Wave went in I had no issues until the latest patch. The last too hops are misleading because they seem to drop icmp packets regardless of whether the issue is happening or not
MTR:
Start: Thu Jan 10 08:06:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.3 0.0 Blizzard 0.0% 10 4.9 1.0 0.5 4.9 1.3
3.|-- 137.221.105.10 0.0% 10 0.5 0.6 0.5 0.7 0.0
4.|-- 137.221.66.20 0.0% 10 0.9 3.1 0.5 25.0 7.7
5.|-- 137.221.83.68 0.0% 10 12.9 18.0 12.7 63.8 16.1
6.|-- 137.221.65.68 0.0% 10 12.9 12.9 12.6 13.2 0.0
7.|-- 137.221.65.1 0.0% 10 15.0 14.9 12.7 23.2 3.3
8.|-- 137.221.65.7 0.0% 10 12.9 13.7 12.7 17.9 1.7
9.|-- 137.221.70.32 0.0% 10 12.8 13.4 12.5 20.1 2.2
10.|-- as11404.sfmix.org 0.0% 10 14.6 14.7 14.5 15.9 0.3
11.|-- cr1-200p-b-be-4.as11404.net 0.0% 10 14.6 14.5 14.2 14.8 0.0
12.|-- cr1-9greatoaks-hu-0-6-0-21-0.bb.as11404.net 0.0% 10 14.3 14.3 14.0 14.5 0.0
13.|-- cr1-pdx-a-hu-0-7-0-1.bb.as11404.net 0.0% 10 34.8 34.8 34.6 35.2 0.0
14.|-- FiberSphere-10000M-PDX.demarc.spectrumnet.us 0.0% 10 34.4 36.1 34.4 50.0 4.8
15.|-- pdx-core-b.fibersphere.net 0.0% 10 34.1 34.1 33.9 34.4 0.0
16.|-- 108.161.17.122 70.0% 10 34.9 34.7 34.5 34.9 0.0
17.|-- x.x.x.x 10.0% 10 36.7 35.6 35.1 36.7 0.4
I will be letting our network teams know about this again and see what we can do. The Last issue was resolved for a few days and this seems to be Wave ISP issues popping up again.
I would ask you to keep posting WinMTRs and Looking glass reports and inform us when things are better or worse. We hope to have more news soon!
As I asked CS directly. it would have been better to keep our main WAVE BROADBAND forum support thread open instead CLOSING so prematurely without proper time to observe whether the “fixes” were final. We had over 60 people and 160 replies going as the CS ESTABLISHED SUPPORT thread for this issue and could have easily continued updating in there allowing auto replies/notifications to notify EVERYONE involved about new developments and that the issue is NOT RESOLVED.
I found this thread and started the continuation here yesterday hoping all from the other thread would find this one.
So what now, CS?Is this the NEW official WAVE thread? Should we all congregate here NOW? Will it get CLOSED and then we have to find another place all over again??
Just leave the forum threads alone please so we don’t have to run around like chickens with our heads cut off. Bad enough this is an issue we are dealing with for 3 months, lets at least make it easy for us to talk to each other for crying out loud/
That out of the way.
Same exact continuation of the original problem. INBOUND PACKET LOSS 20-60% and LAT spikes.
As I’ve have rigorously documented in the previous WAVE BROADBAND FORUM the packet loss occurs in certain server connections to LAX1 while not in others. Packet loss is noted from the beginning of a server connection and persists throughout. The next game or server connection may be completely free of loss from the beginning to end. SAME M.O. as has been happening for MONTHS.
Ive supplied dozens of Looking Glass and MTR results in the previous thread. All info is the same as I just looked and compared. I will repost the same results later since im out of time now.
It looks like some changes were made, can everyone check and see how things are going. Let us know if things are the same or if there have been any improvements.