Wave Broadband California Packet Loss - Nov 22 2018

Technical Support
72

hey guys - piling on here.
i’ve played ow since day 1 of launch. played ladder too since season 1. never had any issue with bandwidth, lag or anything. last couple days i’ve been getting terrible rubber banding and spike lag basically causing me to lag all game once it starts. it looks like things are warping on screen. avg ping usually is like 25-30ms and it will spike to 100-200 with IND going from 20 to 150-200. its funny because i can play a couple games without any issues but once the lag starts ill just keep lag spiking and persists. it’s unplayable. what’s causing it?

fyi i’m in san francisco bay area with wave broadband…

1 Like
73

This is actually an atrocious service by Blizzard so far, its been months since these problems started and no apparent solution have been discovered yet. I have reopened the ticket several times to be linked again to this thread with no solution in sight.

The game’s competitive state is awful enough, with this lag making the entire game unplayable. Can we get any solid updates on what has been done so far and whats a concrete plan to resolving this? I am posting another MTR report from the most recent Overwatch game that I played:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.x.x -    0 |  203 |  203 |    0 |    0 |    1 |    0 |
|                           104.220.x.x -    0 |  203 |  203 |   10 |   19 |   91 |   15 |
|                          174.127.183.54 -    0 |  203 |  203 |   12 |   26 |   82 |   28 |
|        cr1-davis-a-be-20.bb.as11404.net -    0 |  203 |  203 |    4 |   15 |   57 |   19 |
|          cr1-che-b-be-20.bb.as11404.net -    0 |  203 |  203 |   11 |   18 |   65 |   17 |
|     cr1-che-a-te-0-0-0-3.bb.as11404.net -    0 |  203 |  203 |   13 |   18 |   41 |   17 |
| cr1-200p-a-hu-0-7-0-20-0.bb.as11404.net -    0 |  203 |  203 |   14 |   19 |   54 |   16 |
|                       as57976.sfmix.org -    0 |  203 |  203 |   13 |   20 |   41 |   20 |
|              ae1-br01-eqsv5.as57976.net -    0 |  203 |  203 |   12 |   31 | 1314 |   24 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  203 |  203 |   20 |   38 |  436 |   36 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   41 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Any Blizzard/Overwatch personale wanna reply to us?

75

I have contacted the ISP, the servers in question are not owned or operated by Wave. That’s the issue. Furthermore, this is something that Blizzard should be doing for their customers to get THEIR servers (latency or what not) sorted out with the ISPs.

1 Like
77

Hey everybody,

I know this is a frustrating situation but please play nice with each other here. I don’t mind if you’re upset with us - we are investigating to see if there’s anything we can do to help with the problem but the latest tests aren’t as useful as they were the last time we opened a ticket with Wave unfortunately, so it’s not as easy for us to say “the problem is exactly here”. Still, we have some data and are checking it out.

Just make sure you’re laying off eachother. It’s an understandably frustrating situation. Our players want to play our game and I totally respect that. Try to keep this constructive and let’s work together on this one. I don’t want to have to start editing posts to keep this clean.

4 Likes
78

I guess I didn’t do it properly, but I was running the test when in game the lag was 100+ms.

I contacted wave, and they were tracing all the routes the packets take and which server was owned by what ISP. And the issue where the latency was coming from was charter <-> Wave. So, it actually could be Wave talking to charter, or charter’s issue. I don’t quite understand how it works, but as a customer, how do you suggest we “pester” the ISPs? Or get in contact with them with this technical information.

Are you suggesting there is no connection here? Because, Wave (the accused) runs all other games perfectly that i played in past few months. I completely understand that it could still be Wave’s fault, but the issue still is between Wave and Overwatch (or Blizzard). Not Wave and Warframe, or Wave and CoD, or Wave and Fortnite. Why am I experiencing this only on Blizzard’s game? Where’s the connection? Who do we hold accountable and how do we resolve this?

Let’s say if Blizzard is not at fault here, I would love if someone can point me to a path to solving this or getting resolved. May that be through Wave. Thank you. – Keeping it constructive. I want to resolve this, and I want to help in any way I can.

80

Adding on here, I’ve been playing Guild Wars 2, Smash Ultimate (P2P yes I know… but even that is not lagging as bad in Battle Arenas compared to OW), and Fortnite just fine without a single hiccup.

Yes I understand it can be Wave and the network between just Blizzard so it might not be Blizzard’s fault, but we’re giving as much feedback here as we can in case it is.

I don’t get why people feel the need to try to dismiss this thread as if it’s something that is out of Blizzard’s hands and soley on the ISP.

This is why this is my second post on these forums.

Regardless, let’s keep posting our findings and ignore people who think otherwise =)

2 Likes
81

I wonder if the EU problems could be related (if we assume ISP-related pathing issues); as far as I can tell, all US problems are related to Wave in this current batch of problems. I wonder if the EU problems were for related reasons.

Also, please keep in mind that this is over the holidays, so responses and / or work may be understandably slow.

Again, it seems like the key way that users can help diagnose this issue is to collect data, but I don’t think the MTR and traceroutes are particularly helpful for this (as was specifically pointed out in this thread by CS). @Drakuloth, is there anything else that we can do to help you identify a specific problematic node and / or route?

82

Still experiencing this issue. It’s been happening since around Thanksgiving.

Most games will be fine in terms of latency / packet loss but occasionally I’ll get into a game where I get frequent packet loss in of 20-30%. If I leave the game and rejoin it seems to fix the issue, but unfortunately that’s not really a feasible option most of the time.

Reproducible via custom games. I’ve posted the MTR / Looking Glass logs previously in another post.

83

There isn’t a whole lot more I can contribute to this discussion, but I started seeing the same problem just a day ago. Before that I don’t think I’ve ever had any issue with connection to OW servers.

Starting last night I was getting into games with severe packet loss issues. The behavior is completely inconsistent. I’ll get in one game where everything is working just fine, then the next game I’m dropping packets all the time.

I’m also a Wave Broadband user in the San Francisco Bay Area.

I’m seeing this behavior across all game types, custom, quickplay, even training room. I’m too scared to go into any Competitive Games right now, so I can’t say if it’s also happening there.

2 Likes
85

Experiencing latency again on Wave Broadband CA region. Going to continue posting these WinMTR stats assuming they are useful unless stated otherwise:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  278 |  278 |    0 |    0 |    1 |    0 |
|          76-14-176-1.wsac.wavecable.com -    2 |  266 |  263 |    5 |   23 |   98 |   11 |
|                          174.127.183.38 -    3 |  250 |  243 |    5 |   21 |   58 |   18 |
|                       as57976.sfmix.org -    2 |  262 |  258 |   11 |   23 |   53 |   18 |
|              ae1-br01-eqsv5.as57976.net -   16 |  170 |  143 |    0 |   25 |   67 |   30 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    1 |  270 |  268 |   14 |   38 |  349 |   30 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   56 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
86

Packet Loss is WORSE than ever. Connection based INBOUND PACKET LOSS is determeined by BLIZZARDS SERVERS Period.

I can recreate this 100% of the time and submit my list of consecutive connections showing 10 min of packet loss to

one LAX server IP/port and immediately following connection NO PROBLEM for 10 minutes.

Figure this out Blizzard, it’s a good indicator here for your GNOC. 2 months now should be good amount of time for collecting data

now do your due diligence and reach out to whoever you need to follow through.

On today’s Episode of FUN WITH BLIZZARD:

12/23/18

NOTE: ALL CONNECTIONS ARE CONTINUOUS TO LAX1 UNTIL I MANUALLY DISCONNECT.
ALL INBOUND LOSS is apparent from beginning of established connection till the end.
Same with good connections, they are good from beginning to end.

LAX1 24.105.15.227:26531 CONTINUOUS INBOUND LOSS 20-40% 12:20-12:30 PM PST (10 min in training) 12-23-18

LAX1 24.105.15.227:26508 NO PACKET LOSS 12:30-12:40 PM PST (10 min in training) 12-23-18

LAX1 24.105.15.227:26515 NO PACKET LOSS 12:40-12:42 PM PST ( 2 min in training) 12-23-18

LAX1 24.105.15.227:26561 NO PACKET LOSS 12:42-12:44 PM PST ( 2 min in training) 12-23-18

LAX1 24.105.15.227:26594 NO PACKET LOSS 12:44-12:46 PM PST ( 2 min in training) 12-23-18

LAX1 24.105.15.227:26525 NO PACKET LOSS 12:40-12:42 PM PST ( 2 min in training) 12-23-18

LAX1 24.105.15.190:26572 CONTINUOUS INBOUND LOSS 20-40% 12:43-12:53 PM PST (10 min in training) 12-23-18

LAX1 24.105.15.190:26535 NO PACKET LOSS 12:53-1:03 PM PST (10 min in training) 12-23-18

** SO CONNECTION BASED PACKET LOSS!!! THE BLIZZARD SERVER THAT IS CONNECTED TO AT THE TIME IS CORRELATED IN SOME WAY TO THE ISSUE… This should be important for your GNOC.**

MTR and LOOKING GLASS RESULTS BELOW

    Looking Glass Results 
(while connected to LAX1 24.105.15.190 w/ INBOUND LOSS)


TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.424 ms  0.418 ms  0.417 ms Blizzard(24.105.18.2)  0.683 ms  0.758 ms  0.830 ms
 3  137.221.105.14 (137.221.105.14)  1.262 ms  1.262 ms  1.270 ms
 4  137.221.66.22 (137.221.66.22)  1.219 ms  1.233 ms  1.248 ms
 5  137.221.83.68 (137.221.83.68)  12.974 ms  12.985 ms  13.068 ms
 6  137.221.65.68 (137.221.65.68)  12.849 ms  12.805 ms  12.932 ms
 7  137.221.65.1 (137.221.65.1)  12.723 ms  12.822 ms  12.807 ms
 8  137.221.65.7 (137.221.65.7)  12.879 ms  12.880 ms  12.877 ms
 9  137.221.70.32 (137.221.70.32)  12.729 ms  12.712 ms  12.690 ms
10  cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182)  12.950 ms  12.612 ms  12.950 ms
11  cr1-che-b-hu-0-7-0-21-0.bb.as11404.net (192.175.28.109)  14.797 ms  15.216 ms  15.067 ms
12  174.127.183.33 (174.127.183.33)  17.269 ms  16.722 ms  16.690 ms
13  * * *
14  * * *
15  * * *


23/12/2018 21:02:34 UTC
--------------------

TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.363 ms  1.353 ms  1.367 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


23/12/2018 21:02:34 UTC
--------------------

MTR:
Start: Sun Dec 23 21:02:34 2018 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


23/12/2018 21:02:34 UTC
--------------------

MTR:
Start: Sun Dec 23 21:02:34 2018 Blizzard  1.|-- Blizzard                            0.0%    10    0.2   0.3   0.2   0.6   0.0 Blizzard    0.0%    10    0.5   0.6   0.5   0.8   0.0
  3.|-- 137.221.105.14                          0.0%    10    0.6   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.22                           0.0%    10    0.7   2.4   0.5   8.6   3.1
  5.|-- 137.221.83.68                           0.0%    10   12.9  14.6  12.7  30.3   5.5
  6.|-- 137.221.65.68                           0.0%    10   15.6  16.6  12.6  46.7  10.6
  7.|-- 137.221.65.1                            0.0%    10   12.9  17.2  12.7  50.2  11.7
  8.|-- 137.221.65.7                            0.0%    10   12.9  13.1  12.7  15.6   0.7
  9.|-- 137.221.70.32                           0.0%    10   12.6  12.7  12.6  13.2   0.0
 10.|-- cr1-sjo-p200.bb.spectrumnet.us          0.0%    10   12.8  12.9  12.5  13.2   0.0
 11.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404.net  0.0%    10   14.8  14.8  14.7  15.1   0.0
 12.|-- 174.127.183.33                         20.0%    10   15.6  15.7  15.0  16.8   0.4
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0


23/12/2018 21:02:34 UTC
--------------------



MTR to LAX1 24.105.15.190 while having INBOUND PACKET LOSS 20-40% continuous.


|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.x.x -    0 |  264 |  264 |    0 |    0 |   11 |    0 |
|                             76.14.xxx.x -    0 |  264 |  264 |    8 |   16 |   42 |   17 |
|                          174.127.183.24 -    0 |  264 |  264 |    5 |   15 |   54 |   16 |
|                          192.175.28.107 -    0 |  264 |  264 |    7 |   15 |   40 |   14 |
|                          206.197.187.42 -    0 |  264 |  264 |    4 |   17 |   57 |   12 |
|                           137.221.70.33 -    0 |  264 |  264 |    9 |   19 |  158 |   34 |
|                            137.221.65.6 -    0 |  263 |  263 |   15 |   42 | 1920 |   24 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   53 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
88

MY ISP IS WAVE.

MY ORIGINAL CS TICKET and the promoting of CS rep LEVI was what updated this thread for more viability and exposure to all of you. It was renamed WAVE BROADBAND CALIFORNIA PACKET LOSS - 2018. when there were only 2 or 3 relies and stagnant, …

ive been a regular contributor for 3 months and in prior WAVE threads here with more than a handful of many different CS’s . You should go through all my posts before discussing anything further. (i see you keep re-editing your post above and mo reply stands)

I actually have the original WAVEs NOC ticket # that Blizzards GNOC was using a month prior to the current issues when I reopened my original WAVE packet loss ticket (3 months ago). I’ve been providing info to CS and mediating for the various WAVE threads many times, so please do me the courtesy of not diminishing what I am providing here, esp from my network engineer background and being a WAVE customer in this instance who has been part of this ONGOING issue for much more time and effort than you might realize.

Friendly suggestion to you is that you need to be more observant of information before drawing unwarranted conclusions.

1 Like
90

^^Thanks. Hopefully with persistent feedback and CS mediation Blizzard GNOC can finally figure out and tie together why this packet loss is occurring for west coast Wave Broadband users while appearing to have some correlated basis in a connection oriented fashion as confirmed by myself and a few others that recreated what I have been logging (server/ip/port connections)and providing to CS and previous posts in this thread.

So, to be perfectly clear here about the history of this packet loss issue in 2 key points.

1) Issue has to do with packet loss (INBOUND PRIMARILY) and latency spikes for what appears to be predominant WAVE Broadband users on west coast (MYSELF INCLUDED). Not strictly California but Washington and Oregon as well. Customers of other ISPs in WA and OR are also chiming in here, possibly using same infrastructure to route to Blizz west coast server. WAVE is predominantly WA home base extending to OR and California owning former astound and spectrumnet networks across Cali.

2) The connection based correlation. Til I started logging, it was just assumed this was random or intermittent packet loss responsible by WAVE or intermediary peering (routing) partner having some network or hw issues. SO IT WAS VERY CURIOUS that connection mapping showed that inbound packet loss was ONLY exhibited to certain established OW Server connections AT CERTAIN TIMES while NOT others even when connecting to various servers back to back, seconds apart.

Why is this curious? Because if an intermediary network route or hw is dropping inbound packets from Blizzards OW server back to a WAVE customer via a particular route, WHY do we see some dependency on once particular endpoint OW server connection and not consecutive connections? Routing here does not change from one server connection to the next so one would gather that routing issues between Blizz and Wave should produce packet loss that is irrespective of the IP/port connection in this fashion as some of us have observed, logged and reported to CS and posted here.

2 Likes
91

Hi Lads, I see all the treads going back and forth about packet loss to the games on Wave ISP. As I can tell I got complains for packet loss on NTT handoff. Same after the traffic going to Telia in NorCal link and Telia in SoCall and the same to AS57976 peering at SFMIX (https://apps.db.ripe.net/db-web-ui/#/query?searchtext=AS57976#resultsSection).
So now there’s 4 different ISP’s reporting the same issue in different exchange locations. I have boxes at both locations facing either NTT and Telia, but so far I haven’t see any packet loss.

92

Very good information TY!!! Just to be clear, you are having issues via SFMIX?

WAVE currently uses SFMIX Peering Partner for its connectivity with Blizzard (AS57976). I noticed this when first troubleshooting WAVE/Blizz issues like 3 months or so ago.

Prior to SFMIX, maybe a year or so ago Equinix was Wave/Blizzards Peering Partner. They had really bad connectivity causing prior WAVE/Blizzard latency issues and apparently were replaced by SFMIX at some point. This was always on my mind as I noticed this routing change when dealing with the new current issues. I’ve brought up the possibility of SFMIX issues in the past so it makes your post all the more curious to me.

1 Like
93

Another Wave user here in Washington. I’m seeing elevated IND values during certain games and just opened a topic on the subject: Rubber Banding/High IND

94

Quick update on my end guys-
Yesterday I decided to test on my own to see how this situation could be improved. I ended up downloading the 14 day trial for Haste. Been playing on and off for the last couple hours yesterday/today and haven’t had any packet loss issues.
Not sure if just lucky or the issue has improved now or Haste is the temporary fix for us. Let me know your thoughts, all.

95

Experienced this again yesterday. I was playing a Control map and I noticed that in this game the packet loss didn’t actually start until the second round of the map (we didn’t play a third).

96

Experienced it again yesterday as well, both myself and my partner (separate PC, same apartment). As before, restarting the client and rejoining the same game will resolve the issue (although I’m getting warnings about leaver penalties D:)

97

The issue is back in the UK too PS4 servers. Just deleting the game. I’m done with Blizzard and their bs excuses