Wave Broadband California Packet Loss - Nov 22 2018

Technical Support
102

Hey I wanted to pop in and add to this. I was about to make a forum post on this exact same issue. I also have Wave G internet and this has been affecting me for about a month or so now. I’m in Northern Washington State.

These are the things I did in order to try and resolve it myself:

  • Reinstalled network driver
  • Swapped out network card
  • Swapped out network cables
  • Reinstalled windows
  • Multiple game reinstalls

None of these things have been a long term fix as when the issue occurs its a step graph to 2000 ping for about 5 seconds and then back down and again in about 5 seconds. This makes the game unplayable. please let me know how i can help.

103

12-27-18 Ongoing Logging Continued:

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, some with intermittent outbound loss in the single digits at times.

What is odd is that others have this same symptoms also posted in thjis thread, if you connect without loss in the beginning, you can have a good game from beginning to end. Next server connection may be bad from beginning to end. SO given this issue is aimed at intermediary ISP/Peering Partner routing issue (see title), it is odd that the symptoms seem dependent on particular connections to Blizzard Server IP/Port. Behavior is still odd if this issue is supposedly not Blizzard related, just saying. So this point is always on my mind how it correlates.

MTR farther below shows 14% ICMP reply loss @ SFMIX Peering Partner as well as Blizzards routers downstream from SFMIX,
particularly 137.221.65.6 having ICMP loss and 405ms avg ICMP latency.

Connection testing:

LAX1 24.105.15.2:26505 CONTINUOUS INBOUND LOSS 15-30% - 2:00-2:05 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.10.157:26526 CONTINUOUS INBOUND LOSS 15-30% - 2:05-2:10 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.10.157:26586 NO ISSUES/PACKET LOSS - 2:10-2:15 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.10.161:26517 CONTINUOUS INBOUND LOSS 3-20% - 2:15-2:20 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.15.228:26538 NO ISSUES/PACKET LOSS - 2:20-2:25 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.15.228:26506 INTERMITTENT OUTBOUND LOSS 0-7% - 2:25-2:30 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.15.228:26573 CONTINUOUS INBOUND LOSS 7-20% - 2:30-2:35 PM PST ( 5 min in training) 12-27-18

LAX1 24.105.15.228:26553 NO ISSUES/PACKET LOSS - 2:35-2:40 PM PST ( 5 min in training) 12-27-18

12-27-18 Looking Glass

TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.151 ms  2.134 ms  2.133 ms Blizzard(24.105.18.2)  2.753 ms  2.764 ms  2.764 ms
 3  137.221.105.14 (137.221.105.14)  2.799 ms  2.769 ms  2.797 ms
 4  137.221.66.22 (137.221.66.22)  2.769 ms  2.769 ms  2.765 ms
 5  137.221.83.68 (137.221.83.68)  14.787 ms  14.803 ms  14.803 ms
 6  137.221.65.68 (137.221.65.68)  23.583 ms  19.804 ms  19.778 ms
 7  137.221.65.1 (137.221.65.1)  14.388 ms  14.035 ms  14.030 ms
 8  137.221.65.7 (137.221.65.7)  14.021 ms  13.538 ms  13.513 ms
 9  137.221.70.32 (137.221.70.32)  12.580 ms  12.768 ms  12.776 ms
10  cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182)  12.608 ms  13.108 ms  13.082 ms
11  cr1-che-b-hu-0-7-0-21-0.bb.as11404.net (192.175.28.109)  15.066 ms  15.977 ms  15.803 ms
12  174.127.183.33 (174.127.183.33)  16.420 ms  16.127 ms  20.922 ms
13  * * *
14  * * *
15  * * *


27/12/2018 22:19:41 UTC
--------------------

TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.278 ms  0.297 ms  0.300 ms Blizzard(24.105.18.2)  1.199 ms  1.220 ms  1.238 ms
 3  137.221.105.14 (137.221.105.14)  0.544 ms  0.680 ms  0.733 ms
 4  137.221.66.22 (137.221.66.22)  0.620 ms  0.641 ms  0.647 ms
 5  137.221.83.68 (137.221.83.68)  12.896 ms  12.918 ms  12.923 ms
 6  137.221.65.68 (137.221.65.68)  12.746 ms  12.918 ms  12.878 ms
 7  137.221.65.1 (137.221.65.1)  13.003 ms  13.018 ms  13.019 ms
 8  137.221.65.7 (137.221.65.7)  12.796 ms  29.108 ms  29.128 ms
 9  137.221.70.32 (137.221.70.32)  12.635 ms  12.717 ms  12.705 ms
10  cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182)  13.100 ms  12.684 ms  12.882 ms
11  cr1-che-b-hu-0-7-0-21-0.bb.as11404.net (192.175.28.109)  14.736 ms  14.618 ms  14.754 ms
12  * * *
13  * * *
14  * * *
15  * * *


27/12/2018 22:19:41 UTC
--------------------

MTR:
Start: Thu Dec 27 22:19:41 2018 Blizzard  1.|-- Blizzard                            0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard    0.0%    10    0.6   0.6   0.5   1.0   0.0
  3.|-- 137.221.105.14                          0.0%    10    0.6   0.6   0.6   0.8   0.0
  4.|-- 137.221.66.22                           0.0%    10    0.7   0.6   0.5   0.7   0.0
  5.|-- 137.221.83.68                           0.0%    10   12.8  19.2  12.8  72.1  18.6
  6.|-- 137.221.65.68                           0.0%    10   12.7  16.5  12.7  50.1  11.8
  7.|-- 137.221.65.1                            0.0%    10   12.9  15.9  12.7  36.8   7.6
  8.|-- 137.221.65.7                            0.0%    10   12.9  14.8  12.7  32.9   6.3
  9.|-- 137.221.70.32                           0.0%    10   18.4  13.6  12.6  18.4   2.1
 10.|-- cr1-sjo-p200.bb.spectrumnet.us          0.0%    10   13.0  12.8  12.5  13.0   0.0
 11.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404.net  0.0%    10   14.7  14.7  14.6  14.9   0.0
 12.|-- 174.127.183.33                         10.0%    10   68.4  21.2  15.0  68.4  17.7
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0


27/12/2018 22:19:41 UTC
--------------------

MTR:
Start: Thu Dec 27 22:19:41 2018 Blizzard  1.|-- Blizzard                            0.0%    10    0.4   0.3   0.2   0.4   0.0 Blizzard    0.0%    10    0.7   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.14                          0.0%    10    0.7   0.7   0.5   1.4   0.0
  4.|-- 137.221.66.22                           0.0%    10    0.7   0.7   0.5   0.8   0.0
  5.|-- 137.221.83.68                           0.0%    10   12.9  17.6  12.7  60.1  14.9
  6.|-- 137.221.65.68                           0.0%    10   12.9  15.4  12.7  38.1   7.9
  7.|-- 137.221.65.1                            0.0%    10   13.0  16.0  12.8  43.5   9.6
  8.|-- 137.221.65.7                            0.0%    10   12.9  15.6  12.8  38.0   7.9
  9.|-- 137.221.70.32                           0.0%    10   24.7  13.9  12.6  24.7   3.8
 10.|-- cr1-sjo-p200.bb.spectrumnet.us          0.0%    10   13.1  12.9  12.7  13.2   0.0
 11.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404.net  0.0%    10   14.7  14.8  14.6  15.0   0.0
 12.|-- 174.127.183.33                         60.0%    10   57.1  26.0  15.6  57.1  20.7
 13.|-- ???                                    100.0    10    0.0   0.0   0.0   0.0   0.0


27/12/2018 22:19:41 UTC
--------------------



WinMTR to LAX1 24.105.15.228

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.x.x -    0 |   78 |   78 |    0 |    0 |    3 |    0 |
|                             76.14.104.x -    0 |   78 |   78 |    8 |   15 |   32 |   10 |
|                          174.127.183.24 -    0 |   78 |   78 |    8 |   15 |   32 |   13 |
|                          192.175.28.107 -    0 |   78 |   78 |    9 |   14 |   24 |   12 |
|                          206.197.187.42 -   14 |   50 |   43 |   11 |   16 |   27 |   17 |
|                           137.221.70.33 -    0 |   78 |   78 |   10 |   17 |   44 |   15 |
|                            137.221.65.6 -    8 |   52 |   48 |    0 |  405 | 4662 |   27 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   16 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
2 Likes
104

Here is my MTR, Traceroute and ping for this.

PING:

PING 216.243.50.234 (216.243.50.234) 56(84) bytes of data.
64 bytes from 216.243.50.234: icmp_seq=1 ttl=51 time=32.8 ms
64 bytes from 216.243.50.234: icmp_seq=2 ttl=51 time=31.9 ms
64 bytes from 216.243.50.234: icmp_seq=3 ttl=51 time=31.9 ms
64 bytes from 216.243.50.234: icmp_seq=4 ttl=51 time=31.9 ms

— 216.243.50.234 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 31.928/32.194/32.886/0.438 ms

28/12/2018 09:48:40 UTC

PING:
PING 216.243.50.234 (216.243.50.234) 56(84) bytes of data.
64 bytes from 216.243.50.234: icmp_seq=1 ttl=51 time=31.9 ms
64 bytes from 216.243.50.234: icmp_seq=2 ttl=51 time=32.0 ms
64 bytes from 216.243.50.234: icmp_seq=3 ttl=51 time=32.0 ms
64 bytes from 216.243.50.234: icmp_seq=4 ttl=51 time=32.0 ms

— 216.243.50.234 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 31.972/32.007/32.038/0.220 ms

28/12/2018 09:48:41 UTC

TRACEROUTE:
traceroute to 216.243.50.234 (216.243.50.234), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.269 ms 0.252 ms 0.250 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * cr2-sea-b-hu-0-7-0-3.bb.as11404. net (192.175.28.237) 32.223 ms
13 condointernet-2-sea-10000m.demarc.spectrumnet. us (216.243.24.106) 32.808 ms 32.817 ms 32.817 ms
14 216.243.50.129 (216.243.50.129) 32.307 ms 32.355 ms 32.376 ms
15 216.243.50.234 (216.243.50.234) 32.091 ms 32.130 ms 32.136 ms

28/12/2018 09:48:40 UTC

MTR:
Start: Fri Dec 28 09:48:41 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

28/12/2018 09:48:40 UTC

MTR:
Start: Fri Dec 28 09:48:40 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 1.1 0.2 8.4 2.5 Blizzard 0.0% 10 20.4 3.2 0.5 20.4 6.3
3.|-- 137.221.105.10 0.0% 10 0.5 0.7 0.5 0.9 0.0
4.|-- 137.221.66.16 0.0% 10 1.6 0.8 0.5 1.6 0.0
5.|-- 137.221.83.66 0.0% 10 12.9 13.9 12.9 21.4 2.6
6.|-- 137.221.65.68 0.0% 10 12.8 16.0 12.8 43.4 9.6
7.|-- 137.221.65.1 0.0% 10 13.1 12.9 12.7 13.2 0.0
8.|-- 137.221.65.7 0.0% 10 12.9 12.9 12.7 12.9 0.0
9.|-- 137.221.70.32 0.0% 10 12.7 12.7 12.5 13.2 0.0
10.|-- as11404.sfmix. org 10.0% 10 14.7 14.7 14.5 14.8 0.0
11.|-- cr1-529bryant-hu-0-3-0-21-0.bb.as11404. net 0.0% 10 14.7 14.5 14.3 14.7 0.0
12.|-- cr2-sea-b-hu-0-7-0-3.bb.as11404. net 0.0% 10 32.3 32.4 32.2 33.5 0.3
13.|-- condointernet-2-sea-10000m.demarc.spectrumnet. us 0.0% 10 33.1 32.8 32.6 33.1 0.0
14.|-- 216.243.50.129 10.0% 10 32.4 32.4 32.2 32.6 0.0
15.|-- 216.243.50.234 20.0% 10 32.2 32.1 31.9 32.3 0.0

28/12/2018 09:48:40 UTC

TRACEROUTE:
traceroute to 216.243.50.234 (216.243.50.234), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.280 ms 2.284 ms 2.287 ms Blizzard(24.105.18.2) 3.050 ms 3.102 ms 3.125 ms
3 137.221.105.10 (137.221.105.10) 3.060 ms 3.096 ms 3.098 ms
4 137.221.66.16 (137.221.66.16) 3.055 ms 3.060 ms 9.195 ms
5 137.221.83.66 (137.221.83.66) 15.086 ms 15.104 ms 15.108 ms
6 137.221.65.68 (137.221.65.68) 14.890 ms 12.885 ms 12.858 ms
7 137.221.65.1 (137.221.65.1) 12.804 ms 13.032 ms 13.013 ms
8 137.221.65.7 (137.221.65.7) 12.942 ms 12.958 ms 12.938 ms
9 137.221.70.32 (137.221.70.32) 43.024 ms 43.025 ms 41.979 ms
10 as11404.sfmix. org (206.197.187.21) 14.337 ms * 14.508 ms
11 cr1-529bryant-hu-0-3-0-21-0.bb.as11404. net (192.175.28.142) 14.716 ms 14.512 ms 14.368 ms
12 cr2-sea-b-hu-0-7-0-3.bb.as11404. net (192.175.28.237) 32.529 ms 32.605 ms 32.374 ms
13 condointernet-2-sea-10000m.demarc.spectrumnet. us (216.243.24.106) 32.636 ms 32.648 ms 32.629 ms
14 216.243.50.129 (216.243.50.129) 32.567 ms 32.140 ms 32.173 ms
15 216.243.50.234 (216.243.50.234) 32.030 ms 31.748 ms 32.001 ms

28/12/2018 09:48:40 UTC

105

Experiencing same issue here in Norcal.

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 99 | 74 | 1 | 11 | 11 | 11 | 11 |

| 76-14-176-1.wsac.wavecable .com - 0 | 362 | 362 | 8 | 23 | 90 | 73 |

| 174.127.183.42 - 0 | 362 | 362 | 7 | 21 | 53 | 7 |

| cr1-200p-a-be-4.as11404 .net - 0 | 362 | 362 | 8 | 21 | 44 | 30 |

| as57976.sfmix .org - 0 | 362 | 362 | 11 | 22 | 64 | 21 |

| ae1-br01-eqsv5.as57976 .net - 1 | 359 | 358 | 9 | 23 | 75 | 22 |

| xe-0-0-1-1-br02-eqla1.as57976 .net - 1 | 351 | 350 | 15 | 68 | 4950 | 28 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 73 | 0 | 0 | 0 | 0 | 0 |

|________________________________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

106

Wave customer in Northern California as well. Been getting the same rubberbanding randomly. Here’s my log:

PING:
PING 76.14.9.152 (76.14.9.152) 56(84) bytes of data.

— 76.14.9.152 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

29/12/2018 01:22:14 UTC

PING:
PING 76.14.9.152 (76.14.9.152) 56(84) bytes of data.

— 76.14.9.152 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

29/12/2018 01:22:14 UTC

TRACEROUTE:
traceroute to 76.14.9.152 (76.14.9.152), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.231 ms 0.815 ms 0.833 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

29/12/2018 01:22:14 UTC

TRACEROUTE:
traceroute to 76.14.9.152 (76.14.9.152), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.484 ms 3.484 ms 3.495 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

29/12/2018 01:22:14 UTC

MTR:
Start: Sat Dec 29 01:22:14 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 01:22:14 UTC

MTR:
Start: Sat Dec 29 01:22:14 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 01:22:14 UTC

107

I’m a MonkeyBrains customer in SF experiencing similar issues via console. I’m not sure of Waves vs my ISP, but have noticed traffic going through sfmix for both providers, where a lot of my packet loss occurs. Here’s another thread that may help: Random Latency Spikes in Game - #20 by SnowManMan11-1206.

1 Like
108

^^You are not the first to bring up SFMIX… San Francisco Metropolitan Internet Exchange They are a major peering exchange point (AS57976) for various ISPs including WAVE North West Coast to Southern California. For those who don’t know Blizzard uses Airport code for Server Names. LAX (LOS ANGELES) Blizzard LAX1 IP addresses uses SFMIX and also Looking glass traces do show some others in WA, OR as well as CA using SFMIX for return traffic. Blizzard also peers with them for traffic back up North. I have brought up potential concerns of SFMIX peering partner before esp when correlating that as a frequent hop in MTR traffic where ICMP packet loss is always notable to some degree before entering Blizzards Network. However, ICMP prioritization or other factors could account for the ICMP drops as “intended” and not always able to correlate to concurrent gaming UDP packet loss but I’ve always had my suspicions with SFMIX which I have noted to CS in my Tickets and let them iron that info out.

So Wave uses SFMIX to interconnect between Blizzard. You use SFMIX to connect between your ISP Monkey Brains and Blizzard. Someone posting here a week ago using Race Communications I assume Race SFO Bay Area also having issues most likely using SFMIX.

Another informed member here posted a few days ago. Someone who appears to be directly involved/informed about specific Tier 1 Provider (Telia/NTT) inter-connectivity between specific lower tier exchange points. They wrote:

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.

I stressed this to Blizzard CS directly in my Ticket. I felt it might be important for them regarding multiple ISPs having issues and SFMIX being named again.

109

Wave customer here in seattle.
been getting random lag in games (usually I sit around 50ms but randomly It’ll be 100ms and then go farther up into the 500 or so. People are floating around and my abilities are randomly used lol)
here’s my Battle net looking glass

PING:
PING 24.56.241.229 (24.56.241.229) 56(84) bytes of data.
64 bytes from 24.56.241.229: icmp_seq=1 ttl=50 time=46.4 ms
64 bytes from 24.56.241.229: icmp_seq=2 ttl=50 time=46.7 ms
64 bytes from 24.56.241.229: icmp_seq=3 ttl=50 time=40.9 ms
64 bytes from 24.56.241.229: icmp_seq=4 ttl=50 time=51.6 ms

— 24.56.241.229 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 40.948/46.460/51.693/3.806 ms

29/12/2018 03:46:19 UTC

PING:
PING 24.56.241.229 (24.56.241.229) 56(84) bytes of data.
64 bytes from 24.56.241.229: icmp_seq=1 ttl=50 time=41.1 ms
64 bytes from 24.56.241.229: icmp_seq=2 ttl=50 time=41.8 ms
64 bytes from 24.56.241.229: icmp_seq=3 ttl=50 time=41.7 ms
64 bytes from 24.56.241.229: icmp_seq=4 ttl=50 time=46.7 ms

— 24.56.241.229 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 41.184/42.882/46.717/2.229 ms

29/12/2018 03:46:19 UTC

MTR:
Start: Sat Dec 29 03:46:19 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 03:46:19 UTC

MTR:
Start: Sat Dec 29 03:46:19 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.5 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

29/12/2018 03:46:19 UTC

1 Like
110

I’m another Wave customer in Seattle with rubber banding. Happens once every 5-10 games in any game mode. WinMTR from a fresh rubber bandy mystery heroes game:

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 0 522 522 0 0 3 0
67-218-102-107.cust.layer42. net - 0 522 522 5 10 24 10
cr1-tukhe-a-be151.bb.as11404. net - 0 522 522 6 10 27 13
cr1-tukhe-b-te-0-0-0-7.bb.as11404. net - 0 522 522 5 10 28 10
cr2-sea-b-te-0-0-0-15.bb.spectrumnet. us - 0 522 522 7 10 30 9
six.blizzardonline. net - 0 522 522 7 11 39 11
ae1-br01-eqse2.as57976. net - 0 522 522 32 37 130 35
xe-0-0-0-1-br01-eqsv5.as57976. net - 0 522 522 24 32 147 29
xe-0-0-1-1-br02-eqla1.as57976. net - 2 477 469 29 100 4659 38
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
No response from host - 100 105 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

1 Like
111

Hi there, just wanted to chime in and say I’ve been experiencing the same issue for the past few weeks. I’m a Wave Broadband subscriber in the SF Bay Area. The issue occurs every 5 games or so. I see latency spikes up to 1800 ms.

Edit: My experience has been consistent with what is described above by other Wave customers. If a game starts out without any packet loss, I won’t experience packet loss during the entire game. If a game starts out with packet loss, I’ll experience packet loss during the entire game.

No WinMTR to post just yet, but here is a screenshot showing my connection to LAX1 and 70% inbound packet loss:

https://imgur.com/a/tHbyT6Z
112

Took exactly 10 tries in the Practice Range to find a game exhibiting the problem. I was on LAX1 24.105.15.228:26585.

WinMTR follows (I obfuscated the IP address in the first hop):

Host - % Sent Recv Best Avrg Wrst Last
router.asus. com - 0 383 383 0 1 8 1
76-14-x-x.sf-cable.astound. net - 0 383 383 8 25 197 20
agg1-sanmat-a-be-5.bb.as11404. net - 0 383 383 7 22 201 29
br2-sanmat-ae-1.bb.as11404. net - 0 383 383 9 23 195 27
192.175.29.44 - 0 383 383 6 22 204 28
cr1-529bryant-be-2.bb.as11404. net - 0 383 383 9 21 180 22
eqix-sv8.attblizzard. com - 12 264 234 9 22 58 27
ae1-br01-eqsv5.as57976. net - 0 383 383 11 26 198 19
xe-0-0-1-1-br02-eqla1.as57976. net - 1 370 368 16 63 3741 26
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0
No response from host - 100 77 0 0 0 0 0

And a screenshot from that game:

https://imgur.com/a/xlHbBtx
113

Second time around, it only took 4 tries to get into a problematic Practice Range game. I was connected to LAX1, on 24.105.15.228:26592.

WinMTR follows:

Host - % Sent Recv Best Avrg Wrst Last
router.asus. com - 0 376 376 0 1 5 1
76-14-x-x.sf-cable.astound. net - 0 376 376 10 24 93 26
agg1-sanmat-a-be-5.bb.as11404. net - 0 376 376 9 22 48 18
br2-sanmat-ae-1.bb.as11404. net - 0 376 376 10 22 97 17
192.175.29.44 - 0 376 376 6 22 68 23
cr1-529bryant-be-2.bb.as11404. net - 0 376 376 9 22 32 20
eqix-sv8.attblizzard. com - 13 248 216 10 23 45 29
ae1-br01-eqsv5.as57976. net - 0 376 376 10 24 80 25
xe-0-0-1-1-br02-eqla1.as57976. net - 0 376 376 21 36 156 30
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0
No response from host - 100 76 0 0 0 0 0

Hope this helps!

114

The fairest ISP in all of the lands.

115

Well that’s actually a very concise pleasant response I can appreciate. When you actually pay attention to the observations made and volunteer appropriate technical information that possibly helps explain the observed packet loss or lack thereof based on different client server sessions.

The multiple observations stand and are reproducible as stated. Simple observation. You can be connected to the same LAX1 IP for 10-15 minutes straight with continuous packet loss and immediately reconnect back to the same IP (diff. port) and have absolutely zero loss/issue for another 10-15 min. I’ve d one this over and over. As such it was documented and presented for dissemination by Blizzard GNOC, not to start some finger pointing match in this forum. By what means it correlates to the bigger picture was left in Blizzards hands to figure out in this instance. TY for adding another possible explanation for this apparent activity.

So aside from that aspect, the issue remains. We have multiple looking glass traces from multiple ISPs. Wave, Monkey Brains, Race Communications and others within Norcal, OR and WA routing via Norcal to Socal LAX1 and back via SFMIX for many. Same with the reply from the person that has boxes facing various tier 1 providers and lower exchange points pointing out observed issues there in different facing directions.

Anyways, this forum will always be the place to observe and report EVERYTHING and let CS or other technically oriented individuals to help with constructive criticism without unnecessary drama.

This information should already be sufficient to correlate where paths diverge and converge between all the documented traces so far. WAVE is not the only ISP with this issue, but currently all ISPs listed appear to share similar routes. There should already be scrutiny on suspected peering exchange points (SFMIX) given it is a shared peering exchange point for pretty much all the ISPs listed in this forum thread.

4 Likes
116

Also in seattle on Wave with the same issue :frowning:

117

Hmmm, 2nd time Blizz’s network engineers decides to do absolutely nothing and just sit on their thumbs. Have been with Wave for over a decade and have never had issues in all my online gaming with 20+ titles. OW is consistently having issues, it’s Blizz’s end plain and simple, been dealing with 100% packet loss since November 95% of my ranked games.

1 Like
118

Wave customer here from Redmond, WA. OW is pretty much unplayable now due to this issue. Noticed some other WA posters in here, so instead of making a new thread i’ll post my results as well.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                         router.asus.com -    1 |  493 |  491 |    0 |    0 |    0 |    0 |
|                           174.127.246.1 -    0 |  501 |  501 |    1 |    1 |   24 |    1 |
|                   No response from host -  100 |  101 |    0 |    0 |    0 |    0 |    0 |
|     cr2-sea-a-be100-4000.bb.as11404.net -    0 |  501 |  501 |    1 |    1 |    6 |    1 |
|            cr2-sea-b-be1.bb.as11404.net -    0 |  501 |  501 |    1 |    1 |    4 |    2 |
|                  six.blizzardonline.net -    0 |  501 |  501 |    1 |    2 |   35 |    2 |
|              ae1-br01-eqse2.as57976.net -    0 |  501 |  501 |   29 |   30 |  110 |   29 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |  501 |  501 |   29 |   30 |   82 |   29 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    1 |  486 |  483 |   26 |   46 | 2618 |   27 |
|              be2-pe01-eqla1.as57976.net -   16 |  309 |  261 |   28 |   28 |   30 |   28 |
|                           24.105.30.129 -    4 |  445 |  431 |   29 |   29 |   32 |   29 |

as you can see, 16% packet loss on the 2nd to last hop. it’s pretty bad.

and here’s looking glass.

TRACEROUTE:
traceroute to 174.127.246.52 (174.127.246.52), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.340 ms  1.343 ms  1.340 ms Blizzard(24.105.18.2)  2.895 ms  2.881 ms  2.879 ms
 3  137.221.105.14 (137.221.105.14)  2.409 ms  2.406 ms  2.406 ms
 4  137.221.66.22 (137.221.66.22)  2.377 ms  2.386 ms  2.387 ms
 5  137.221.83.68 (137.221.83.68)  14.334 ms  14.342 ms  14.342 ms
 6  137.221.65.68 (137.221.65.68)  13.762 ms  16.241 ms  16.207 ms
 7  137.221.65.1 (137.221.65.1)  16.159 ms  16.146 ms  16.141 ms
 8  137.221.65.7 (137.221.65.7)  16.136 ms  16.131 ms  16.126 ms
 9  137.221.70.32 (137.221.70.32)  16.365 ms  12.705 ms  12.675 ms
10  as11404.sfmix.org (206.197.187.21)  14.575 ms  14.498 ms  14.582 ms
11  cr1-529bryant-hu-0-3-0-21-0.bb.as11404.net (192.175.28.142)  16.160 ms  15.485 ms  15.200 ms
12  cr2-sea-b-hu-0-7-0-3.bb.as11404.net (192.175.28.237)  32.404 ms  32.418 ms  32.407 ms
13  condointernet-2-sea-10000m.demarc.spectrumnet.us (216.243.24.106)  32.781 ms  32.461 ms  32.489 ms
14  174.127.246.52 (174.127.246.52)  34.594 ms  34.334 ms  34.419 ms


30/12/2018 07:33:04 UTC
--------------------

TRACEROUTE:
traceroute to 174.127.246.52 (174.127.246.52), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.203 ms  0.205 ms  0.206 ms Blizzard(24.105.18.2)  0.447 ms  0.610 ms  0.622 ms
 3  137.221.105.14 (137.221.105.14)  0.749 ms  0.761 ms  0.912 ms
 4  137.221.66.22 (137.221.66.22)  0.608 ms  0.610 ms  0.613 ms
 5  137.221.83.68 (137.221.83.68)  12.870 ms  12.884 ms  12.887 ms
 6  137.221.65.68 (137.221.65.68)  12.713 ms  12.767 ms  12.761 ms
 7  137.221.65.1 (137.221.65.1)  14.599 ms  14.260 ms  14.238 ms
 8  137.221.65.7 (137.221.65.7)  12.922 ms  12.933 ms  12.931 ms
 9  137.221.70.32 (137.221.70.32)  12.483 ms  12.577 ms  12.554 ms
10  as11404.sfmix.org (206.197.187.21)  14.598 ms  14.546 ms  14.487 ms
11  cr1-529bryant-hu-0-3-0-21-0.bb.as11404.net (192.175.28.142)  14.541 ms  14.648 ms  14.287 ms
12  cr2-sea-b-hu-0-7-0-3.bb.as11404.net (192.175.28.237)  32.359 ms  32.278 ms  32.220 ms
13  condointernet-2-sea-10000m.demarc.spectrumnet.us (216.243.24.106)  32.764 ms  32.753 ms  32.637 ms
14  174.127.246.52 (174.127.246.52)  34.232 ms  34.414 ms  34.395 ms


30/12/2018 07:33:04 UTC
--------------------

MTR:
Start: Sun Dec 30 07:33:04 2018 Blizzard  1.|-- Blizzard                                      0.0%    10    0.2   0.3   0.2   0.6   0.0 Blizzard              0.0%    10    0.5   1.6   0.5  10.2   3.0
  3.|-- 137.221.105.14                                    0.0%    10    0.5   0.9   0.5   4.1   1.1
  4.|-- 137.221.66.22                                     0.0%    10    0.8   0.8   0.5   1.2   0.0
  5.|-- 137.221.83.68                                     0.0%    10   13.2  13.7  12.5  21.7   2.7
  6.|-- 137.221.65.68                                     0.0%    10   12.9  13.3  12.8  15.8   0.7
  7.|-- 137.221.65.1                                      0.0%    10   13.2  16.2  12.7  40.3   8.5
  8.|-- 137.221.65.7                                      0.0%    10   12.6  12.9  12.5  13.2   0.0
  9.|-- 137.221.70.32                                     0.0%    10   12.5  12.8  12.5  14.7   0.7
 10.|-- as11404.sfmix.org                                10.0%    10   14.7  14.9  14.4  15.8   0.0
 11.|-- cr1-529bryant-hu-0-3-0-21-0.bb.as11404.net       10.0%    10   14.3  14.5  14.3  14.7   0.0
 12.|-- cr2-sea-b-hu-0-7-0-3.bb.as11404.net              10.0%    10   32.2  32.2  32.0  32.5   0.0
 13.|-- condointernet-2-sea-10000m.demarc.spectrumnet.us 20.0%    10   32.4  33.7  32.2  38.2   2.1
 14.|-- 174.127.246.52                                    0.0%    10   34.9  35.1  34.4  39.3   1.4


30/12/2018 07:33:04 UTC
--------------------

MTR:
Start: Sun Dec 30 07:33:04 2018 Blizzard  1.|-- Blizzard                                      0.0%    10    0.3   0.5   0.2   2.2   0.3 Blizzard              0.0%    10    0.7   1.1   0.5   5.1   1.3
  3.|-- 137.221.105.14                                    0.0%    10    0.6   0.8   0.5   2.2   0.5
  4.|-- 137.221.66.22                                     0.0%    10    0.6   0.9   0.5   3.3   0.7
  5.|-- 137.221.83.68                                     0.0%    10   12.8  12.8  12.6  12.9   0.0
  6.|-- 137.221.65.68                                     0.0%    10   12.8  13.3  12.8  15.8   0.7
  7.|-- 137.221.65.1                                      0.0%    10   13.5  17.4  12.8  40.4   9.4
  8.|-- 137.221.65.7                                      0.0%    10   12.9  12.9  12.6  13.2   0.0
  9.|-- 137.221.70.32                                     0.0%    10   13.0  12.9  12.5  14.9   0.7
 10.|-- as11404.sfmix.org                                10.0%    10   15.5  14.9  14.5  15.8   0.0
 11.|-- cr1-529bryant-hu-0-3-0-21-0.bb.as11404.net       10.0%    10   16.0  14.7  14.2  16.0   0.4
 12.|-- cr2-sea-b-hu-0-7-0-3.bb.as11404.net              10.0%    10   32.5  32.2  32.0  32.5   0.0
 13.|-- condointernet-2-sea-10000m.demarc.spectrumnet.us  0.0%    10   32.4  33.6  32.3  38.5   2.0
 14.|-- 174.127.246.52                                   10.0%    10   36.5  35.4  34.3  39.3   1.5


30/12/2018 07:33:04 UTC
--------------------

some servers are fine, but i usually connect to ones that make comp unplayable.

i don’t have this issue with any other game.

119

how did you get the data formatted so nicely btw?

120

I’m having the same problem, Wave Broadband in Northern California. Every few games my ping goes from 45 (normal) to 100-200 with major packet loss, making the game unplayable. Sometimes I can quit the game and reconnect to the same match and it will play fine.

It looks like the issue is: sfmix.org

Pathping:

Tracing route to 24.105.10.156 over a maximum of 30 hops

  0  DESKTOP [192.168.1.48] 
  1  192.168.7.1 
  2  104.220.96.1 
  3  cr1-rhe-b-be152.bb.as11404.net [174.127.183.20] 
  4  cr1-rhe-a-be-1.as11404.net [192.175.29.158] 
  5  cr1-che-b-be-2.as11404.net [192.175.29.161] 
  6  cr1-che-a-te-0-0-0-2.bb.as11404.net [192.175.28.6] 
  7  cr1-200p-a-hu-0-7-0-20-0.bb.as11404.net [192.175.28.107] 
  8  as57976.sfmix.org [206.197.187.42] 
  9  ae1-br01-eqsv5.as57976.net [137.221.70.33] 
 10  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
 11     *        *        *     
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           DESKTOP [192.168.1.48] 
                                0/ 100 =  0%   |
  1    2ms     0/ 100 =  0%     0/ 100 =  0%  192.168.7.1 
                                0/ 100 =  0%   |
  2   20ms     0/ 100 =  0%     0/ 100 =  0%  104.220.96.1 
                                0/ 100 =  0%   |
  3   18ms     0/ 100 =  0%     0/ 100 =  0%  cr1-rhe-b-be152.bb.as11404.net [174.127.183.20] 
                                0/ 100 =  0%   |
  4   18ms     0/ 100 =  0%     0/ 100 =  0%  cr1-rhe-a-be-1.as11404.net [192.175.29.158] 
                                0/ 100 =  0%   |
  5   20ms     0/ 100 =  0%     0/ 100 =  0%  cr1-che-b-be-2.as11404.net [192.175.29.161] 
                                0/ 100 =  0%   |
  6   19ms     0/ 100 =  0%     0/ 100 =  0%  cr1-che-a-te-0-0-0-2.bb.as11404.net [192.175.28.6] 
                                0/ 100 =  0%   |
  7   20ms     0/ 100 =  0%     0/ 100 =  0%  cr1-200p-a-hu-0-7-0-20-0.bb.as11404.net [192.175.28.107] 
                                3/ 100 =  3%   |
  8  ---     100/ 100 =100%    97/ 100 = 97%  as57976.sfmix.org [206.197.187.42] 
                                0/ 100 =  0%   |
  9   23ms     3/ 100 =  3%     0/ 100 =  0%  ae1-br01-eqsv5.as57976.net [137.221.70.33] 
                                3/ 100 =  3%   |
 10  101ms     6/ 100 =  6%     0/ 100 =  0%  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 

Trace complete.

Traceroute

Tracing route to 24.105.10.156 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.7.1 
  2    18 ms    21 ms    12 ms  104.220.96.1 
  3    13 ms    22 ms    17 ms  cr1-rhe-b-be152.bb.as11404.net [174.127.183.20] 
  4    21 ms    26 ms    19 ms  cr1-rhe-a-be-1.as11404.net [192.175.29.158] 
  5    28 ms    19 ms    15 ms  cr1-che-b-be-2.as11404.net [192.175.29.161] 
  6    24 ms    21 ms    20 ms  cr1-che-a-te-0-0-0-2.bb.as11404.net [192.175.28.6] 
  7    24 ms    15 ms    18 ms  cr1-200p-a-hu-0-7-0-20-0.bb.as11404.net [192.175.28.107] 
  8    17 ms    24 ms    20 ms  as57976.sfmix.org [206.197.187.42] 
  9    25 ms    24 ms    20 ms  ae1-br01-eqsv5.as57976.net [137.221.70.33] 
 10    28 ms    33 ms    31 ms  xe-0-0-1-1-br02-eqla1.as57976.net [137.221.65.6] 
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.
1 Like
121

Note to ALL affected people: This issue has not shown up on east coast servers. When I duo queue with people on east coast servers, i’ve yet to see this happen once. Its not terrible ping and its much better than needing to reset adapter or game. VPN’ing over East should work too though I haven’t tried it as yet.

Cheers!