Wave Broadband California Packet Loss - Nov 22 2018

Technical Support
86

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

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

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

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

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

On today’s Episode of FUN WITH BLIZZARD:

12/23/18

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

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

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

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

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

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

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

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

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

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

MTR and LOOKING GLASS RESULTS BELOW

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


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


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

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


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

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


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

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


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



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


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

MY ISP IS WAVE.

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

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

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

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

1 Like
90

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

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

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

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

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

2 Likes
91

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

92

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

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

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

1 Like
93

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

94

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

95

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

96

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

97

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

98

Issue is still present Blizzard. Inbound Packet loss present everyday (in the same way as documented by me and others previously) since my last post with spiking LAT on certain server ip/port connections.

I am not going to waste time reposing or posting new connection ip/port info or corresponding looking glass mtr info since it would be no different than the multitude of previous data dumps Ive been posting here. Just a simple, YES, problem is still present 12/26/18.

99

Hi there friends,

I am popping in to let you know we are still looking in to these reports. Posting WinMTRs and Looking glass reports can help us narrow down the issue. Most of the time when it is a specific ISP, we must find the node and report the problem to them.

Thanks for baring with us!

/Nathardrick

3 Likes
100

I played games with Haste trial as well, haven’t experienced the lag spikes in-game (Quick Play and Competitive). In training grounds, with Haste, the lag is horrible (100+ms).

Average ping for an entire day was in 36-37 ms, improved from the 41-42 ms I get from not using Haste and when the lag is not happening.

I still haven’t played enough to reproduce the 100+ ms lag spikes within QP or Comp using Haste. It may be I just got lucky yesterday and there was no lag, and not Haste doing anything good for me.

1 Like
101

Yeah- my ping isn’t better with Haste but there’s rubberbanding when I don’t use it.

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