Wave Broadband California Packet Loss - Nov 22 2018

Jmack-1384 · November 25, 2018, 8:25am

Starting on Thursday November 22, 2018 all 3 people on my network have started getting huge amounts of packet loss every 2-5 games. The problem is temporarily resolved by leaving the game and rejoining, or as soon as a new game starts. When this happens our latency also doubles from ~25MS to ~50MS.

I have a WinMTR log and screenshots of the network graph for an entire game but if I put them in here I think my post is being deleted. The WinMTR shows no packet loss anywhere and the screenshot is showing:
PPS IN ~14.5
PPS OUT ~64.5
LOSS IN ~38.6%
LOSS OUT ~0.0%

The game server IP was 24.105.9.13

Anyone know what it could be? Thanks!

Legendary-1586 · November 25, 2018, 8:30am

I’m one of the 3 people mentioned above that is experiencing this issue. We have tried restarting our router, running a ‘scan and repair’ on the game, updating our gpu drivers, restarted our computers / clients both, etc. Nothing is working D: We are experiencing the issue both on LAN and wifi.

Drakuloth · November 26, 2018, 5:47am

Hey you two,

You’re both on Wave Broadband, it looks like, and we’ve gotten a couple reports in your area. Can we have you post some WinMTR and Looking Glass reports while the issue is happening? We’d like to see if this is the same situation as we saw a month or so ago.

I edited the post title to make sure players in your area know where to go for information.

Thanks!

DamnVoices-1262 · November 26, 2018, 6:44am

I am a Wave customer in Northern California. I currently have EXTREME packet loss and high latency spikes to my local server.

Starting 2-3 days ago I have high inbound packet loss spiking back and forth 15-30%. This is continuous packet loss with intermittent spikes as high as 40%. Also LAT/RTT spikes. My Latency is higher on average during this time with big spikes. Prior to this Normal stable Latency is 40ms for me to LAX1, which is my primary gaming server. Currently Latency on avg is above 50ms with erratic spikes upwards of 150ms back down etc. Very erratic.

This is very similar to an issue Blizzard had with Wave a month ago which was resolved at that time yet has resurfaced with the same pattern of behavior, something I have reopened and have a current ticket with Blizzard at this time.

If I change region and connect to Europe or Asia CDG1 or ICN1 servers I have zero packet loss and stable but high ping obviously due to geographical distance. It does however shed light that routing from Wave to these foreign servers appears to take a different path bypassing the problem.

Current Accompanying MTR. Some IP address info has been redacted for privacy posting here.

MTR to LAX1 24.105.13.184

|-------------------------------------------------------- | WinMTR statistics | Host - % |------------------------------------------------|------| | x.x.x.x - 0 | | x.x.x.x - | 174.127.183.24 - 0 | 82 | 82 | | 192.175.28.107 - 0 | 82 | 82 | | 206.197.187.42 - 3 | 75 | 73 | | 137.221.70.33 - 0 | | 137.221.65.6 - 0 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | | No response from host - 100 | 17 | |________________________________________________|______| ----------------------------------||
|
| Sent | Recv | Best | Avrg | Wrst | Last |
------|------|------|------|------||
82 | 82 | 0 | 0 | 1 | 0 |
0 | 82 | 82 | 4 | 16 | 41 | 15 |<–Wave ISP
3 | 15 | 40 | 4 |<–Wave ISP
4 | 14 | 29 | 15 |<–Wave ISP
5 | 17 | 84 | 22 |<–Bliz/SFMIX Peering Partner
82 | 82 | 11 | 18 | 48 | 13 |<–Blizzard ISP
76 | 76 | 14 | 156 | 4303 | 54 |<–Blizzard ISP
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
0 | 0 | 0 | 0 | 0 |
______|______|______|______|______|

Note: Per above, Although there may not necessarily be any correlation it is noted that some % of ICMP packet loss is observed at 206.197.187.42 which is the SFMIX Peering Partner that routes/connects between WAVE Networks to Blizzards Networks.

.
.
.
Looking Glass Return routing Info:

TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
1 Blizzard Blizzard 3.907 ms 3.901 ms 3.904 ms
2 37.244.22.130 (37.244.22.130) 4.794 ms 4.814 ms 4.819 ms
3 24.105.30.166 (24.105.30.166) 4.823 ms 4.834 ms 4.837 ms
4 137.221.66.4 (137.221.66.4) 5.885 ms 5.888 ms 5.890 ms
5 137.221.68.72 (137.221.68.72) 12.232 ms 12.248 ms 12.252 ms
6 137.221.65.7 (137.221.65.7) 12.069 ms 8.723 ms 8.731 ms
7 137.221.70.32 (137.221.70.32) 8.475 ms 8.414 ms 8.399 ms
8 cr1-sjo-p200.bb.spectrumnet. us (206.223.116.182) 8.750 ms 8.669 ms 8.795 ms
9 cr1-che-b-hu-0-7-0-21-0.bb.as11404. net (192.175.28.109) 10.637 ms 10.605 ms 10.693 ms
10 174.127.183.33 (174.127.183.33) 10.957 ms 12.686 ms *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

26/11/2018 06:38:57 UTC

TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.054 ms 1.040 ms 1.038 ms
2 37.244.22.130 (37.244.22.130) 1.935 ms 1.940 ms 1.941 ms
3 24.105.30.166 (24.105.30.166) 2.004 ms 2.158 ms 2.972 ms
4 137.221.66.4 (137.221.66.4) 3.001 ms 3.002 ms 3.004 ms
5 137.221.68.72 (137.221.68.72) 9.360 ms 9.362 ms 9.364 ms
6 137.221.65.7 (137.221.65.7) 9.205 ms 8.687 ms 8.735 ms
7 137.221.70.32 (137.221.70.32) 8.429 ms 8.432 ms 8.405 ms
8 cr1-sjo-p200.bb.spectrumnet. us (206.223.116.182) 8.723 ms 8.762 ms 8.777 ms
9 cr1-che-b-hu-0-7-0-21-0.bb.as11404. net (192.175.28.109) 10.615 ms 10.625 ms 10.591 ms
10 174.127.183.33 (174.127.183.33) 10.843 ms 12.687 ms 12.038 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

26/11/2018 06:38:57 UTC

MTR:
Start: Mon Nov 26 06:38:57 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.22.130 0.0% 10 0.6 0.6 0.5 0.9 0.0
3.|-- 24.105.30.166 0.0% 10 0.7 1.0 0.7 2.1 0.3
4.|-- 137.221.66.4 0.0% 10 1.7 1.7 1.4 2.2 0.0
5.|-- 137.221.68.72 0.0% 10 8.3 8.4 8.3 8.5 0.0
6.|-- 137.221.65.7 0.0% 10 8.8 8.7 8.4 9.0 0.0
7.|-- 137.221.70.32 0.0% 10 8.3 8.3 8.2 8.4 0.0
8.|-- cr1-sjo-p200.bb.spectrumnet. us 0.0% 10 8.5 8.5 8.3 8.8 0.0
9.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404. net 0.0% 10 10.3 10.4 10.3 10.5 0.0
10.|-- 174.127.183.33 50.0% 10 11.4 17.2 11.3 40.4 12.9
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

26/11/2018 06:38:57 UTC

MTR:
Start: Mon Nov 26 06:38:57 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.22.130 0.0% 10 0.5 0.5 0.5 0.6 0.0
3.|-- 24.105.30.166 0.0% 10 1.0 1.0 0.9 1.1 0.0
4.|-- 137.221.66.4 0.0% 10 1.5 1.6 1.5 1.7 0.0
5.|-- 137.221.68.72 0.0% 10 8.4 9.2 8.4 14.7 1.9
6.|-- 137.221.65.7 0.0% 10 8.3 10.2 8.3 26.7 5.7
7.|-- 137.221.70.32 0.0% 10 8.8 8.6 8.2 9.0 0.0
8.|-- cr1-sjo-p200.bb.spectrumnet. us 0.0% 10 8.6 8.5 8.3 8.8 0.0
9.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404. net 0.0% 10 10.4 10.4 10.3 10.5 0.0
10.|-- 174.127.183.33 20.0% 10 11.1 13.0 11.1 25.4 5.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

26/11/2018 06:38:57 UTC

Neo-15548 · November 26, 2018, 5:44pm

Was linked to this in response to a support ticket by Chris from Blizzard. Would just like to add that I am also a Wave Broadband customer in Northern California and have been experiencing packet loss. Issue ID #65982292 for my MTR tests for 2 servers, approximately 2 games each test.

DamnVoices-1262 · November 26, 2018, 7:36pm

Thanks so much Logan for setting up the Wave thread with better viability. It appears more have chimed in on exact same packet loss/latency issues from Wave ISP to Blizzard OW server in S. Cali (LAX1).

Given that this may be related to the work Wave was doing a month ago when your GNOC was in collaboration via WAVE TICKET # 4592463 and also given that more affected customers are posting in this technical thread is Blizzard (re)opening this case with WAVE directly on all our behalves as they did a month ago when this was an issue or am I and the other Wave customers posting in the thread to contact WAVE directly about this?

I rather not spread the resources thin by creating duplicate support requests with multiple NOC’s if in fact Blizzard is already mediating this as before.

Thank You

EDIT: 7pm PST Still having issues tonight. Same. 16-30% inbound packet loss and spiking Latency.

Jmack-1384 · November 27, 2018, 4:44am

I didn’t have Looking Glass when I took this, but here is my WinMTR from a game that had the packet loss issue. I’ve been playing for a few hours tonight with no issues though. so that’s good.

edit: packet loss is back tonight.

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

| WinMTR statistics |

Host - %	Sent	Recv	Best	Avrg	Wrst	Last
192.168.0.1 - 0	520	520	0	1	107	0
172.92.6.129 - 0	520	520	1	2	97	1
cr1-200p-t9-1.bb.as54858 .net - 0	520	520	0	2	102	1
agg1-200p-b-t7-1.bb.spectrumnet .us - 0	520	520	0	2	159	1
cr1-200p-b-te-0-0-0-6.bb.spectrumnet .us - 0	520	520	1	2	100	1
cr1-200p-a-be-4.as11404 .net - 0	520	520	1	2	100	1
as57976.sfmix .org - 0	520	520	2	3	104	2
ae1-br01-eqsv5.as57976 .net - 0	520	520	2	5	122	2
xe-0-0-1-1-br02-eqla1.as57976 .net - 1	496	495	9	89	4625	14
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
No response from host - 100	104	0	0	0	0	0
________________________________________________	______	______	______	______	______	______

lorethon-1432 · November 27, 2018, 4:55am

Just got out chat with GM for WoW support re: latency issues. Our issues matched the ones mentioned above (winMTR and tracerts the same, etc). Issue is temporarily solved by relogging. Latency is random, recent, and relatively frequent. He suggested we chime in here noting that we are seeing this on the wow side of things too.

|                             192.168.0.1 -    0 |  527 |  527 |    3 |    9 |   22 |    8 |

|         67-218-102-101.cust.layer42.net -    0 |  527 |  527 |    6 |    9 |   25 |   11 |

|                          174.127.182.72 -    0 |  527 |  527 |    9 |   21 |   93 |   19 |

|      br1-ptw-a-ae-1-0.bb.spectrumnet.us -    0 |  527 |  527 |    9 |   14 |   48 |   14 |

|         cr1-pohe-a-be-10.bb.as11404.net -    0 |  527 |  527 |    8 |   13 |   26 |   13 |

|    cr1-pohe-b-hu-0-6-0-1.bb.as11404.net -    1 |  523 |  522 |    8 |   13 |   28 |   13 |

|     cr2-sea-b-hu-0-7-0-4.bb.as11404.net -    1 |  519 |  516 |    9 |   14 |   32 |   11 |

|                  six.blizzardonline.net -    0 |  527 |  527 |   10 |   14 |   46 |   15 |

|              ae1-br01-eqse2.as57976.net -    0 |  527 |  527 |   55 |   61 |  109 |   66 |

|       xe-0-0-1-1-br02-eqch2.as57976.net -    6 |  414 |  390 |   55 |  192 | 3490 |   60 |

|              be2-pe02-eqch2.as57976.net -    0 |  527 |  527 |   55 |   59 |   71 |   61 |

|                           24.105.62.129 -    1 |  516 |  513 |   55 |   60 |   79 |   71 |

DamnVoices-1262 · November 27, 2018, 5:39am

I concur. The issue is intermittent. Currently I do have packet loss (again) after
I had a few decent games earlier today before 6pm PST with connections to LAX1 where there was zero packet loss or latency spikes for a few games. Then , a short time later the issue presents itself and persists for some duration.

I then leave the server go into arcade or training to try and make another connection to LAX1 and everything is fine again. No packet loss or issues for a short while , then it starts all over again, down the line.

Horkin-1762 · November 27, 2018, 7:06am

I’m seeing this same issue out of Portland, OR. Fibersphere is my provider. How do I see which server I’m connected to?

Latency goes to around 80ms and IND roughly 100ms somewhat randomly and is only solved by leaving the game and logging out.

Normal latency is around 45ms with IND 20ms.

Legendary-1586 · November 27, 2018, 7:44am

we got the IP address during a game in overwatch by hitting ‘ctrl’ + ‘shift’ + ‘n’, you will then see the game server’s IP address in the top left corner. Not sure if that’s completely correct, that’s just what we did

Ibaraius · November 27, 2018, 9:14pm

Horkin

It is possible depending how you are routed. If you post a WinMTR test we can see if it is related.

Neo-15548 · November 29, 2018, 12:03am

Just an update, if it helps, I am still getting the packet loss and the lag spikes. For some reason I see it worse in the training grounds (about 200ms) and 49 -ish in competitive and quick play. Is there a course of action for this issue?

What should we as players do to help Blizzard solve this? Or do we have to contact Wave about it? Would really like some clarification.

DamnVoices-1262 · December 11, 2018, 10:17pm

Packet loss started again yesterday after about 7-10 days of clear sailing. Same issue. 20-30% inbound packet loss only. Some latency spiking. Normal latency 37-43ms to LAX1 and CURRENTLY spiking 60-80ms concurrent with packet loss.

Neo-15548 · December 12, 2018, 3:38am

Same thing happening here, Wave says the problem is not with them, it is with the server that it is talking to which is under Charter, another ISP.

Jmack-1384 · December 12, 2018, 4:27am

I’m still having the problem. Going to open a WaveG ticket. Maybe if we hit them with enough tickets they will look into it.

Nanohaxial-1503 · December 12, 2018, 4:33am

Same here. Seeing packet loss spike over 30% in some games. I saw this issue previously the other week and posted about it then, although it seemed to resolve itself after a day or two.

DamnVoices-1262 · December 13, 2018, 4:08am

NEW INFO!

OK I have been extensively testing this and can say with almost complete certainty this intermittent issue is SERVER CONNECTION BASED. I have already updated this issue to blizzard CS.

The packet loss is present immediately when connecting to a particular IP/PORT in the pool of addresses that LAX1 uses, I assume it’s pool of load balanced IP’s.
I noticed this when it was happening prior a few weeks ago. Id connect to LAX1 and have issues from the get go, or I’d connect another time and not have any… so tonight I logged my connections and activity and time.

Tonight, play connected to LAX1 back to back, connected to various IP and Ports that are assigned to it.
So here is the detailed info for tonight all matches (connections) are contiguous, back to back.

LAX1 24.105.10.140:26504 - 6:15pm PST No problem Played for @ 10 min

LAX1 24.105.11.2:26580 - 6:30pm PST No problem Played for @ 10 min

LAX1 24.104.14.67:26613 - 6:40pm PACKET LOSS!!! for whole time connected @
15min

Immediately after…

LAX1 24.105.11.2:26580 - 7:05pm no Problem connected for 15 min

There is an intermittent issue BECAUSE it is dependent on the particular Server IP connection. In the span of minutes I can have bad connection to one of the load balanced IP addresses belonging to LAX1 pool, followed by a completely good connection to another. fully able to duplicate this now and gather more data on other IP connections.

If this was not an issue on Blizzards end, I cannot explain this kind of behavior.

This is DEFINITELY not reminiscent of a packet loss in transit at some given router.

It should not produce such symptoms that hinge on the particular OW Server IP yet it does.

I ALSO ran a looking glass trace back to be from Blizzard WHILE connected to each server listed above. The routes back are identical in the traces. I have provided these to CS and will post here as well.

Looking Glass performed while connected to LAX1 24.104.14.67:26613 around 6:40pm PST 12-12-18 Packet Loss

Looking Glass
TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.681 ms 0.672 ms 0.675 ms Blizzard(24.105.18.2) 1.595 ms 1.602 ms 1.603 ms
3 137.221.105.14 (137.221.105.14) 0.785 ms 0.878 ms 0.972 ms
4 137.221.66.22 (137.221.66.22) 0.909 ms 0.920 ms 0.922 ms
5 137.221.83.68 (137.221.83.68) 13.167 ms 13.250 ms 13.257 ms
6 137.221.65.68 (137.221.65.68) 13.317 ms 12.924 ms 12.901 ms
7 137.221.65.1 (137.221.65.1) 12.901 ms 12.908 ms 12.908 ms
8 137.221.65.7 (137.221.65.7) 12.869 ms 12.876 ms 12.891 ms
9 137.221.70.32 (137.221.70.32) 12.582 ms 12.950 ms 12.936 ms
10 cr1-sjo-p200.bb.spectrumnet. us (206.223.116.182) 12.678 ms 12.912 ms 12.894 ms
11 cr1-che-b-hu-0-7-0-21-0.bb. as11404 .net (192.175.28.109) 14.782 ms 14.933 ms 15.217 ms
12 174.127.183.33 (174.127.183.33) 16.032 ms 16.055 ms 16.108 ms
13 * * *
14 * * *
15 * * *

13/12/2018 02:33:05 UTC

TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.686 ms 2.691 ms 2.691 ms Blizzard(24.105.18.2) 3.129 ms 3.131 ms 9.884 ms
3 137.221.105.14 (137.221.105.14) 3.092 ms 3.094 ms 3.138 ms
4 137.221.66.22 (137.221.66.22) 3.057 ms 3.082 ms 3.083 ms
5 137.221.83.68 (137.221.83.68) 15.250 ms 15.297 ms 15.300 ms
6 137.221.65.68 (137.221.65.68) 17.513 ms 13.168 ms 13.148 ms
7 137.221.65.1 (137.221.65.1) 13.060 ms 13.066 ms 13.093 ms
8 137.221.65.7 (137.221.65.7) 13.126 ms 13.143 ms 13.148 ms
9 137.221.70.32 (137.221.70.32) 12.688 ms 12.734 ms 12.856 ms
10 cr1-sjo-p200.bb.spectrumnet. us (206.223.116.182) 12.835 ms 12.620 ms 12.608 ms
11 cr1-che-b-hu-0-7-0-21-0.bb. as11404. net (192.175.28.109) 14.674 ms 14.681 ms 14.911 ms
12 174.127.183.33 (174.127.183.33) 15.756 ms 15.936 ms 15.995 ms
13 * * *
14 * * *
15 * * *

13/12/2018 02:33:05 UTC

MTR:
Start: Thu Dec 13 02:33:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.8 0.2 3.2 0.8 Blizzard 0.0% 10 1.1 4.1 0.5 20.8 6.6
3.|-- 137.221.105.14 0.0% 10 0.6 3.0 0.5 20.2 6.1
4.|-- 137.221.66.22 0.0% 10 0.7 1.2 0.5 5.9 1.6
5.|-- 137.221.83.68 0.0% 10 12.8 12.8 12.7 12.9 0.0
6.|-- 137.221.65.68 0.0% 10 12.8 173.7 12.8 866.6 289.3
7.|-- 137.221.65.1 0.0% 10 162.9 37.4 12.8 162.9 52.4
8.|-- 137.221.65.7 0.0% 10 12.8 12.9 12.7 13.3 0.0
9.|-- 137.221.70.32 0.0% 10 22.0 14.9 12.5 22.0 3.1
10.|-- cr1-sjo-p200.bb.spectrumnet. us 0.0% 10 13.3 12.9 12.5 13.3 0.0
11.|-- cr1-che-b-hu-0-7-0-21-0.bb. as11404. net 0.0% 10 24.6 16.8 14.7 25.6 4.3
12.|-- 174.127.183.33 80.0% 10 15.7 18.9 15.7 22.1 4.5
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/12/2018 02:33:05 UTC

MTR:
Start: Thu Dec 13 02:33:05 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.5 0.2 2.5 0.7 Blizzard 0.0% 10 0.8 5.4 0.5 21.3 8.5
3.|-- 137.221.105.14 0.0% 10 0.6 2.8 0.5 20.0 6.1
4.|-- 137.221.66.22 0.0% 10 0.5 1.4 0.5 5.3 1.7
5.|-- 137.221.83.68 0.0% 10 12.7 12.7 12.6 12.9 0.0
6.|-- 137.221.65.68 0.0% 10 12.7 151.4 12.6 646.7 233.8
7.|-- 137.221.65.1 0.0% 10 162.8 37.3 12.7 162.8 52.3
8.|-- 137.221.65.7 0.0% 10 12.7 13.1 12.7 15.5 0.7
9.|-- 137.221.70.32 0.0% 10 21.8 14.8 12.6 21.8 3.0
10.|-- cr1-sjo-p200.bb.spectrumnet. us 0.0% 10 13.2 12.9 12.5 13.4 0.0
11.|-- cr1-che-b-hu-0-7-0-21-0.bb. as11404. net 0.0% 10 24.4 16.9 14.8 25.3 4.2
12.|-- 174.127.183.33 90.0% 10 21.4 21.4 21.4 21.4 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/12/2018 02:33:05 UTC

24.105.11.2:26556 NO PROBLEMS around 6:55pm PST 12-12-18

Looking Glass
TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.633 ms 0.615 ms 0.615 ms Blizzard(24.105.18.2) 1.492 ms 1.492 ms 1.655 ms
3 137.221.105.14 (137.221.105.14) 1.547 ms 1.549 ms 1.667 ms
4 137.221.66.22 (137.221.66.22) 1.490 ms 1.492 ms 1.493 ms
5 137.221.83.68 (137.221.83.68) 13.393 ms 13.604 ms 13.617 ms
6 137.221.65.68 (137.221.65.68) 16.201 ms 15.423 ms 15.377 ms
7 137.221.65.1 (137.221.65.1) 126.592 ms 126.031 ms 126.009 ms
8 137.221.65.7 (137.221.65.7) 13.540 ms 13.538 ms 13.535 ms
9 137.221.70.32 (137.221.70.32) 12.968 ms 12.967 ms 12.926 ms
10 cr1-sjo-p200.bb.spectrumnet. us (206.223.116.182) 13.281 ms 13.344 ms 13.385 ms
11 cr1-che-b-hu-0-7-0-21-0.bb. as11404. net (192.175.28.109) 14.846 ms 14.777 ms 14.999 ms
12 174.127.183.33 (174.127.183.33) 16.492 ms 16.121 ms 16.140 ms
13 * * *
14 * * *
15 * * *

13/12/2018 02:46:01 UTC

TRACEROUTE:
traceroute to 76.14.108.xxx (76.14.108.xxx), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.774 ms 0.751 ms 0.750 ms Blizzard(24.105.18.2) 1.620 ms 1.643 ms 1.644 ms
3 137.221.105.14 (137.221.105.14) 1.696 ms 1.695 ms 1.696 ms
4 137.221.66.22 (137.221.66.22) 1.637 ms 1.639 ms 1.640 ms
5 137.221.83.68 (137.221.83.68) 13.521 ms 13.539 ms 13.525 ms
6 137.221.65.68 (137.221.65.68) 16.325 ms 15.413 ms 15.367 ms
7 137.221.65.1 (137.221.65.1) 126.563 ms 126.010 ms 125.991 ms
8 137.221.65.7 (137.221.65.7) 13.513 ms 13.519 ms 13.518 ms
9 137.221.70.32 (137.221.70.32) 12.961 ms 12.991 ms 12.971 ms
10 cr1-sjo-p200.bb.spectrumnet .us (206.223.116.182) 13.041 ms 13.223 ms 13.278 ms
11 cr1-che-b-hu-0-7-0-21-0.bb.as11404 .net (192.175.28.109) 14.761 ms 14.757 ms 14.997 ms
12 174.127.183.33 (174.127.183.33) 16.027 ms 16.025 ms 16.078 ms
13 * * *
14 * * *
15 * * *

13/12/2018 02:46:01 UTC

MTR:
Start: Thu Dec 13 02:46:01 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.7 0.2 4.6 1.2 Blizzard 0.0% 10 0.6 0.5 0.5 0.6 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 0.6 0.4 0.7 0.0
5.|-- 137.221.83.68 0.0% 10 27.6 14.3 12.7 27.6 4.7
6.|-- 137.221.65.68 0.0% 10 12.9 28.0 12.7 124.4 35.4
7.|-- 137.221.65.1 0.0% 10 51.8 16.8 12.7 51.8 12.3
8.|-- 137.221.65.7 0.0% 10 21.8 13.7 12.6 21.8 2.8
9.|-- 137.221.70.32 0.0% 10 12.6 13.1 12.5 17.0 1.2
10.|-- cr1-sjo-p200.bb.spectrumnet .us 0.0% 10 13.3 12.8 12.6 13.3 0.0
11.|-- cr1-che-b-hu-0-7-0-21-0.bb .as11404.net 0.0% 10 15.0 14.8 14.7 15.0 0.0
12.|-- 174.127.183.33 30.0% 10 17.1 18.3 15.0 33.4 6.7
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/12/2018 02:46:01 UTC

MTR:
Start: Thu Dec 13 02:46:01 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.7 0.6 0.4 1.0 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.6 1.1 0.5 5.1 1.2
5.|-- 137.221.83.68 0.0% 10 31.4 14.7 12.7 31.4 5.9
6.|-- 137.221.65.68 0.0% 10 12.9 25.1 12.7 111.0 31.0
7.|-- 137.221.65.1 0.0% 10 75.9 19.2 12.6 75.9 19.9
8.|-- 137.221.65.7 0.0% 10 82.9 23.1 12.7 82.9 23.4
9.|-- 137.221.70.32 0.0% 10 12.8 12.6 12.5 12.8 0.0
10.|-- cr1-sjo-p200.bb.spectrumnet .us 0.0% 10 12.8 12.8 12.7 13.0 0.0
11.|-- cr1-che-b-hu-0-7-0-21-0.bb .as11404.net 0.0% 10 14.9 14.8 14.6 15.1 0.0
12.|-- 174.127.183.33 70.0% 10 15.5 15.3 15.1 15.5 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

13/12/2018 02:46:01 UTC

I’ll continue making more connections to verify this trend further, I just wanted to post this up with what i have first. TY.

DamnVoices-1262 · December 13, 2018, 4:41am

OK More Interesting Info adding to my last post above.

I connected to LAX1 continuously back to back in Training. Sometimes it would rotate me into a non priority server like PSE1, SAC1, SAE1 etc… these have no issues so I’d immediately back out and fish for LAX1 connections… here’s a detailed timeline for 15 minutes of hunting server connections:

LAX1 24.104.14.67:26567 8:14PM PST 12-12-18 -INBOUND PACKET LOSS 15-20%

LAX1 24.104.14.67:26605-8:16PM PST 12-12-18 No Packet Loss

LAX1 24.104.14.67:26504 -8:18PM PST 12-12-18 No Packet Loss

LAX1 24.104.14.67:26508 -8:19PM PST 12-12-18 No Packet Loss

LAX1 24.104.14.67:26507 -8:20PM PST 12-12-18 No Packet Loss

LAX1 24.104.11.2:26563 -8:21PM PST 12-12-18 No Packet Loss

LAX1 24.104.11.2:26518 -8:22PM PST 12-12-18 No Packet Loss

LAX1 24.104.11.2:26530 -8:23PM PST 12-12-18 INBOUND PACKET LOSS 15-20%

LAX1 24.104.14.67:26534 -8:25PM PST 12-12-18 INBOUND PACKET LOSS 15-20%

LAX1 24.104.11.2:26563 -8:27PM PST 12-12-18 No Packet Loss

LAX1 24.104.14.67:26551 -8:30PM PST 12-12-18 INBOUND PACKET LOSS 15-20%

In EVERY instance, packet loss starts IMMEDIATELY when a socket is established to the given IP/PORT and lasts THE WHOLE DURATION until disconnect. I did this repeatedly. This issue diverges fr om IP alone and appears to be dependent on port connected to.

For instance, I connected to LAX1 24.104.11.2:26530 at 8:23PM PST which had Packet loss, while a differ connection to 24.104.11.2:26563 -8:27PM was Free of issues upon connection.

NEVER does it appear that packet loss and latency issues start in the middle of a given connection. I cannot document that the issue has shown itself while connected. I have only seen newly initiated connections either have an issue or they don’t right from the start till end.

I don’t know what the deal is, just trying to provide as much pertinent information and observations that may help resolve this madness that we have been enduring off and on for a while now.

Destrado-1495 · December 13, 2018, 2:59pm

I can confirm that I also am experiencing noticeable packet loss on LAX1 on Wave Broadband in Bellevue, WA. It only started after the last update, but that may be anecdotal.