Wave Broadband California Packet Loss - Nov 22 2018

Technical Support
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!

122

having same issue with wave broadband, near Bellevue, WA

US-WEST
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   Linksys.wavecable.com -    0 | 1035 | 1035 |    0 |    0 |   12 |    0 |
|c-66-235-0-1.sea.wa.customer.broadstripe.net  0 | 1035 | 1035 |    6 |   33 |  335 |   16 |
|     cr1-duvallhe-a-be150.bb.as11404.net -    0 | 1035 | 1035 |    4 |   27 |  229 |   10 |
|             br1-jvo-ae-0.bb.as11404.net -    0 | 1035 | 1035 |    7 |   30 |  256 |   17 |
|            cr1-bds-be-10.bb.as11404.net -    0 | 1035 | 1035 |    5 |   29 |  234 |   23 |
|  cr2-sea-b-hu-0-5-0-20-0.bb.as11404.net -    0 | 1035 | 1035 |    5 |   31 |  271 |   29 |
|                  six.blizzardonline.net -    0 | 1035 | 1035 |    4 |   31 |  259 |   29 |
|              ae1-br01-eqse2.as57976.net -    0 | 1035 | 1035 |   32 |   58 |  299 |   38 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    1 | 1031 | 1030 |   32 |   56 |  264 |   41 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    1 | 1023 | 1021 |   32 |   67 | 3522 |   39 |
|              be2-pe02-eqla1.as57976.net -    4 |  921 |  892 |   33 |   54 |  254 |   46 |
|        lax-eqla1-ia-bons-03.as57976.net -    4 |  925 |  897 |   34 |   55 |  253 |   53 |
|                           24.105.30.129 -    5 |  881 |  842 |   33 |   54 |  260 |   51 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

US-CENTRAL
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                   Linksys.wavecable.com -    0 |  211 |  211 |    0 |    0 |    5 |    0 |
|c-66-235-0-1.sea.wa.customer.broadstripe.net  0 |  211 |  211 |   11 |   36 |  320 |   33 |
|     cr1-duvallhe-a-be150.bb.as11404.net -    0 |  211 |  211 |   11 |   32 |  323 |   33 |
|             br1-jvo-ae-0.bb.as11404.net -    0 |  211 |  211 |    9 |   29 |  190 |   37 |
|            cr1-bds-be-10.bb.as11404.net -    0 |  211 |  211 |   10 |   31 |  191 |   29 |
|  cr2-sea-b-hu-0-5-0-20-0.bb.as11404.net -    0 |  211 |  211 |   12 |   34 |  323 |   29 |
|                  six.blizzardonline.net -    0 |  211 |  211 |    5 |   31 |  289 |   41 |
|              ae1-br01-eqse2.as57976.net -    0 |  211 |  211 |   58 |   82 |  361 |   90 |
|       xe-0-0-1-1-br02-eqch2.as57976.net -    0 |  211 |  211 |   55 |   78 |  254 |   91 |
|              be2-pe01-eqch2.as57976.net -    0 |  211 |  211 |   58 |   79 |  367 |   72 |
|        chi-eqch2-ia-bons-02.as57976.net -    0 |  211 |  211 |   60 |   81 |  368 |   82 |
|                           24.105.62.129 -    0 |  211 |  211 |   56 |   80 |  368 |   69 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
1 Like
124

Seattle area with WaveG here, can confirm I have the same issue. I am glad I found this thread, the latency spikes is driving me nuts.

I will try to capture the file via WinMTR next time when the spike happens. Hopefully this can get resolved soon.

Happy holiday guys.

126

I reproduced the issue a few more times, this time without my router. The first WinMTR was a game where latency was closer to normal and packet loss was maybe around 10%. The other two were more severe with higher latency and packet loss.

1:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            104.156.x.x  -    0 |  340 |  340 |    0 |    1 |   32 |    1 |
|                   No response from host -  100 |   69 |    0 |    0 |    0 |    0 |    0 |
|     cr2-sea-a-be100-4000.bb.as11404.net -    0 |  340 |  340 |    0 |    0 |   16 |    0 |
|            cr2-sea-b-be1.bb.as11404.net -    0 |  340 |  340 |    0 |    0 |    2 |    1 |
|                  six.blizzardonline.net -    0 |  340 |  340 |    0 |    1 |   23 |    1 |
|              ae1-br01-eqse2.as57976.net -    0 |  340 |  340 |   25 |   26 |   60 |   25 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |  340 |  340 |   21 |   23 |  159 |   21 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  340 |  340 |   25 |   32 |  140 |   32 |
|                   No response from host -  100 |   69 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|

2:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            104.156.x.x  -    0 |  313 |  313 |    1 |    1 |   11 |    1 |
|                   No response from host -  100 |   63 |    0 |    0 |    0 |    0 |    0 |
|     cr2-sea-a-be100-4000.bb.as11404.net -    0 |  313 |  313 |    0 |    0 |   15 |    0 |
|            cr2-sea-b-be1.bb.as11404.net -    0 |  313 |  313 |    0 |    0 |    8 |    0 |
|                  six.blizzardonline.net -    0 |  313 |  313 |    0 |    0 |   39 |    1 |
|              ae1-br01-eqse2.as57976.net -    0 |  313 |  313 |   25 |   27 |   70 |   25 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |  313 |  313 |   21 |   23 |   74 |   21 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  313 |  313 |   25 |   33 |  161 |   46 |
|                   No response from host -  100 |   63 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|

3:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                            104.156.x.x  -    0 |  305 |  305 |    1 |    1 |   11 |    1 |
|                   No response from host -  100 |   62 |    0 |    0 |    0 |    0 |    0 |
|     cr2-sea-a-be100-4000.bb.as11404.net -    0 |  305 |  305 |    0 |    0 |    3 |    0 |
|            cr2-sea-b-be1.bb.as11404.net -    0 |  305 |  305 |    0 |    0 |    2 |    1 |
|                  six.blizzardonline.net -    0 |  305 |  305 |    0 |    1 |   43 |    1 |
|              ae1-br01-eqse2.as57976.net -    0 |  305 |  305 |   25 |   26 |   71 |   25 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |  305 |  305 |   21 |   23 |  136 |   21 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  305 |  305 |   25 |   33 |  344 |   27 |
|                   No response from host -  100 |   62 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
127

Hi folks, another wave broadband user here from Woodburn, OR. also experiencing this issue. I opened a support ticket for help with it and it looks like I’m not alone! I already provided an WinMTR log and some other things in my support ticket but I figured I’d drop them here as well.

Here is a 2:50 video recording of the issue in action: chi#12286 Overwatch Wave Broadband routing issue sample - YouTube

and a WinMTR taken during that same game

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

|                                      WinMTR statistics                                   |

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

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

|                             192.168.0.1 -    0 | 1325 | 1325 |    0 |    0 |    2 |    0 |

|          67-218-102-93.cust.layer42.net -    0 | 1325 | 1325 |    6 |    9 |   20 |   11 |

|                          174.127.182.44 -    0 | 1325 | 1325 |    7 |   10 |   19 |    9 |

|           cr1-pdx-a-be-4.bb.as11404.net -    0 | 1325 | 1325 |    7 |   11 |   21 |   10 |

|           cr2-sea-b-be-2.bb.as11404.net -    0 | 1325 | 1325 |   12 |   15 |   25 |   15 |

|                  six.blizzardonline.net -    0 | 1325 | 1325 |   12 |   15 |   53 |   16 |

|              ae1-br01-eqse2.as57976.net -    0 | 1325 | 1325 |   37 |   42 |  160 |   64 |

|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 | 1325 | 1325 |   26 |   34 |  160 |   31 |

|       xe-0-0-1-1-br02-eqla1.as57976.net -    1 | 1301 | 1298 |   38 |   64 | 4615 |   49 |

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

This issue has been going on a pretty long time for what seems like a large group of people.

129

Wave customer here in the Bay Area with the exact same issues as others have reported.

130

Norther California Wave customer experiencing the same issues on Xbox one along with several friends. Just chiming in. Hope this issue gets settled soon.

131

Northern California Wave customer, same issue. Haven’t been able to play in 2-3 weeks.

132

I am a Sail Internet user in NorCal. Pretty similar MTR as the Wave customers above. Blizzard closed 2 of my tickets saying that it was my ISP’s (Sail) fault. My assumption is that most players from the Bay (maybe North West Coast) are affected by

xe-0-0-1-1-br02-eqla1.as57976

which isn’t run every packet but seems to have a high RTT (Round Trip Time). I tried to ask why we were being routed to this node but Blizzard support ignored what I wrote and blamed it on one of my ISP’s servers. The problem is, we aren’t experiencing lag spikes, but a constant increase in ping. I thought it had something to do with the winter update but unsure.

133

Hi all.
Wave Broadband customer here. Latency is getting pretty unbearable, especially when playing with friends. I can provide an MTR the next time it happens.

Despite all this, have a Happy New Years!

134

Okay went into QuickPlay 15 minutes ago and gathered WinMTR.
Also I play on PC edition.
The game network console (ctrl shift N) showed I had between 30-50% packet loss. Indicated I had 115ms ping but I know it was much much worse.
Looks like when it gets near “as57976” it runs into problems.

## WinMTR statistics

|Host|%|Sent|Recv|Best|Avrg|Wrst|Last|
|192.168.1.1|0|202|202|0|0|11|0|
|76-14-176-1.wsac.wavecable.com|0|202|202|10|24|111|22|
|174.127.183.42|0|202|202|11|21|68|17|
|cr1-200p-a-be-4.as11404.net|0|202|202|12|21|71|18|
|as57976.sfmix.org|0|202|202|12|22|64|23|
|ae1-br01-eqsv5.as57976.net|0|202|202|15|23|131|21|
|xe-0-0-1-1-br02-eqla1.as57976.net|0|202|202|22|36|157|25|
|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|
|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|
135

Same issues here in Seattle, WA. Packet loss 20% of games. Wave G broadband.

HOWEVER - we were able to come up with a workaround using a VPN.

We use Private Internet Access and had it connect to the Seattle server. This completely solved all of our packet loss problems while keeping our ping relatively low.

It makes sense, since the VPN uses a different set of connections, but it sucks that we have to lose our gigabit speed in order to play Overwatch.

Hope this gets resolved soon.

1 Like
136

How badly does the VPN affect your ping?

138

Tracerts (using WINMTR) to the same lax1 server:

Before VPN

Ping ~ 40ms

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

| WinMTR statistics |

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

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

| router.asus. com- — 0 | 29 | 29 | 0 | 0 | 1 | 0 |

| br1-joule-v100.bb.as54858.net- 0 | 29 | 29 | 1 | 2 | 11 | 2 |

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

| cr2-sea-a-be100-4000.bb.as11404. net - 0 | 29 | 29 | 0 | 0 | 1 | 1 |

| cr2-sea-b-be1.bb.as11404. net - 0 | 29 | 29 | 0 | 0 | 1 | 1 |

| [six.blizzardonline. net] - 0 | 29 | 29 | 0 | 1 | 14 | 1 |

| [ae1-br01-eqse2.as57976. net]- 0 | 29 | 29 | 26 | 27 | 47 | 26 |

| xe-0-0-0-1-br01-eqsv5.as57976. net - 17 | 18 | 15 | 0 | 21 | 47 | 20 |

| xe-0-0-1-1-br02-eqla1.as57976. net - 0 | 29 | 29 | 26 | 30 | 62 | 32 |

After VPN:

Ping ~ 44ms (+4)

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

| WinMTR statistics |

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

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

| 10.10.10.1 - --------------------- 0 | 29 | 29 | 0 | 0 | 1 | 1 |

|[ip-1-44-244-173.seattle.us.northamericancoax. com] 0 | 29 | 29 | 1 | 1 | 1 | 1 |

| [six.blizzardonline. net]- ------------- 0 | 29 | 29 | 1 | 1 | 6 | 1 |

| [ae1-br01-eqse2.as57976. net] - 0 | 29 | 29 | 29 | 30 | 48 | 30 |

| [xe-0-0-0-1-br01-eqsv5.as57976. net] - 0 | 29 | 29 | 19 | 20 | 38 | 19 |

| xe-0-0-1-1-br02-eqla1.as57976. net] - 0 | 29 | 29 | 30 | 38 | 87 | 61 |

Apologize for the formatting. It looks like before the VPN it makes 8 hops (9 if you include the timeout #3), and after the VPN it makes 6.

I think the odd thing is that they both pass through

xe-0-0-0-1-br01-eqsv5.as57976. net

but with the VPN on there is no packet loss.

I reran the test an additional time with 50 packets sent, and got the same results.

before VPN (sorry cant post links, remove the spaces)
https:// imgur. com/a/Kiquixw

after VPN
https:// imgur. com/a/U7rUjJN

Hope this helps.

139

Hey gang!

We’ve received news from our network technicians that a fix was recently implemented by Wave. Everyone should retest at this time, but please also try clearing your network device caches.

Power Cycling Your Network Devices

IP Release, Renew, and Flush DNS

If issues persist after doing those steps, we’ll want fresh WinMTR reports to reflect the current state of things.

Running WinMTR

You can include the WinMTR results in a reply to the forum post. Place it between rows of ticks (`) for formatting:

```
Like this.
```

5 Likes
140

Hey guys!

I’m experiencing this same issue, and really want to start my comp placements, so I decided to do something about it.

I dug up the reddit handles of some network engineers / svps at Wave G. I sent them a link to this thread and two of them got back to me saying they would forward to the appropriate people. I’ve been chatting with one of them back and forth the last few days, and today received these messages indicating that the problem should be fixed now!

FYI we did get a response from a network engineer at Blizzard and they are working with our Core Network Engineering team. The dates when people are saying that the issue started are roughly the same time we and Blizzard made changes to our peering (added more locations and capacity which should make things better not worse) So we’re working with them to see if that’s related. May be something else but that’s where they are starting.

Then, a couple hours later:

Hello, we did find and correct a network config issue on our side that may have been causing this. Could you check and let me know if things are working now? Also, if things look to be fixed feel free to update the Blizzard support post (my old Battle . net account seems to be inactive so I can’t post). Would appreciate hearing if this fixed the issue.

Here’s hoping it’s actually fixed!

1 Like