This issue has been going on a pretty long time for what seems like a large group of people.
Wave customer here in the Bay Area with the exact same issues as others have reported.
Norther California Wave customer experiencing the same issues on Xbox one along with several friends. Just chiming in. Hope this issue gets settled soon.
Northern California Wave customer, same issue. Haven’t been able to play in 2-3 weeks.
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.
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!
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|
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.
How badly does the VPN affect your ping?
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.
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.
You can include the WinMTR results in a reply to the forum post. Place it between rows of ticks (`) for formatting:
```
Like this.
```
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!
Wow really! Thank you so much! Would you be able to get any details on what was causing this @ WaveG?
I didn’t get a whole lot of details, but the guy I chatted with was really nice and helpful-- he evens said he used to play Starcraft & Diablo on Battle. net himself haha! All signs appeared to point to their AS11404 backbone, but I’m not actually sure what the final configuration changes they needed to make were.
I’m at work now, haven’t been able to test the changes myself, but here’s hoping it worked
I’m seeing horrid lag (3-4) second constant cycles as has been described many times here. I’ve been attempting to track when it happens, and it is definitely only on specific servers. I’m on Wave Broadband in Seattle, WA.
It’s been going on for a couple weeks now, and affects probably 1 out of every 4 games when I am unlucky and get a bad server.
WinMTR statistics
Host | % | Sent | Recv | Best | Avrg | Wrst | Last |
router.asus.com | 0 | 300 | 300 | 0 | 0 | 1 | 0 |
174.127.246.1 | 0 | 300 | 300 | 1 | 1 | 5 | 1 |
No response from host | 100 | 61 | 0 | 0 | 0 | 0 | 0 |
cr2-sea-a-be100-4000.bb.as11404.net | 0 | 300 | 300 | 1 | 1 | 3 | 2 |
cr2-sea-b-be1.bb.as11404.net | 0 | 300 | 300 | 1 | 1 | 4 | 2 |
six.blizzardonline.net | 0 | 300 | 300 | 1 | 2 | 21 | 2 |
ae1-br01-eqse2.as57976.net | 0 | 300 | 300 | 27 | 28 | 70 | 27 |
xe-0-0-0-1-br01-eqsv5.as57976.net | 0 | 300 | 300 | 22 | 23 | 92 | 22 |
xe-0-0-1-1-br02-eqla1.as57976.net | 0 | 300 | 300 | 27 | 34 | 185 | 28 |
also played a little bit of deathmatch on the same server (LAX1), no packet loss! hopefully it stays that way.
EDIT: 2 matches later back to ~40% packet loss. i think i’m just going to quit OW for a while, lol. the weird thing is it’s the same server every time. sometimes it works just fine, sometimes it’s awful. you never know until you connect, so i just can’t play the game because it’s like flipping a coin.
Heya… I’m another Wave Broadband customer who’s been having this issue (chatted with Blizzard CS on Twitter about it), and it was looking really good today until just a few minutes ago when I had another of those games. My ping is usually around 45 in good conditions, but on a messed up game, it starts 60-80 and gets worse when there’s more action happening in game. The spikes are up to around 120, but performance is significantly worse than a 120ms ping would imply, and the net graph shows frequent orange blocks.
I was really hoping it was fixed today, but that doesn’t appear to be the case. Imma go cry into my cereal now.
Still able to reproduce this issue. I don’t have a modem since I just directly connect the ethernet cable to the wall in my apartment. I did reproduce it both with and without my router. I also ran the ipconfig commands, both when using then router and then again after bypassing the router.
With Router:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 448 | 448 | 0 | 0 | 14 | 1 |
| 104.156.x.x - 0 | 448 | 448 | 1 | 1 | 33 | 1 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
| cr2-sea-a-be100-4000.bb.as11404.net - 0 | 448 | 448 | 0 | 0 | 14 | 0 |
| cr2-sea-b-be1.bb.as11404.net - 0 | 448 | 448 | 0 | 0 | 15 | 0 |
| six.blizzardonline.net - 0 | 448 | 448 | 0 | 0 | 34 | 0 |
| ae1-br01-eqse2.as57976.net - 0 | 448 | 448 | 25 | 26 | 137 | 25 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 448 | 448 | 20 | 23 | 120 | 22 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 1 | 436 | 435 | 25 | 65 | 3895 | 28 |
| No response from host - 100 | 90 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
With Router:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| router.asus.com - 0 | 465 | 465 | 0 | 0 | 12 | 0 |
| 104.156.x.x - 0 | 465 | 465 | 1 | 1 | 26 | 1 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
| cr2-sea-a-be100-4000.bb.as11404.net - 0 | 465 | 465 | 0 | 0 | 19 | 0 |
| cr2-sea-b-be1.bb.as11404.net - 1 | 461 | 460 | 0 | 0 | 15 | 1 |
| six.blizzardonline.net - 0 | 465 | 465 | 0 | 1 | 36 | 0 |
| ae1-br01-eqse2.as57976.net - 0 | 465 | 465 | 25 | 26 | 117 | 25 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 465 | 465 | 20 | 23 | 172 | 21 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 465 | 465 | 25 | 32 | 174 | 30 |
| No response from host - 100 | 94 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Without Router:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 104.156.x.x - 0 | 373 | 373 | 1 | 1 | 24 | 1 |
| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |
| cr2-sea-a-be100-4000.bb.as11404.net - 0 | 373 | 373 | 0 | 0 | 2 | 0 |
| cr2-sea-b-be1.bb.as11404.net - 0 | 373 | 373 | 0 | 0 | 2 | 1 |
| six.blizzardonline.net - 0 | 373 | 373 | 0 | 0 | 17 | 0 |
| ae1-br01-eqse2.as57976.net - 0 | 373 | 373 | 25 | 27 | 100 | 26 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 373 | 373 | 21 | 22 | 101 | 21 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 373 | 373 | 25 | 37 | 923 | 29 |
| No response from host - 100 | 75 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Without Router:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 104.156.x.x - 0 | 306 | 306 | 1 | 1 | 72 | 1 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
| cr2-sea-a-be100-4000.bb.as11404.net - 0 | 306 | 306 | 0 | 0 | 19 | 0 |
| cr2-sea-b-be1.bb.as11404.net - 0 | 306 | 306 | 0 | 0 | 4 | 0 |
| six.blizzardonline.net - 0 | 306 | 306 | 0 | 0 | 30 | 0 |
| ae1-br01-eqse2.as57976.net - 0 | 306 | 306 | 25 | 26 | 67 | 29 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 306 | 306 | 21 | 23 | 139 | 21 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 306 | 306 | 25 | 34 | 585 | 30 |
| No response from host - 100 | 62 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
For comparison’s sake, a game without issues:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 104.156.x.x - 0 | 369 | 369 | 1 | 1 | 15 | 1 |
| No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
| cr2-sea-a-be100-4000.bb.as11404.net - 0 | 369 | 369 | 0 | 0 | 22 | 0 |
| cr2-sea-b-be1.bb.as11404.net - 0 | 369 | 369 | 0 | 0 | 3 | 0 |
| six.blizzardonline.net - 0 | 369 | 369 | 0 | 0 | 21 | 0 |
| ae1-br01-eqse2.as57976.net - 0 | 369 | 369 | 25 | 26 | 86 | 25 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 369 | 369 | 21 | 23 | 84 | 21 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 1 | 354 | 351 | 25 | 53 | 3518 | 26 |
| No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
Unfortunately, still experiencing this issue here. Wave customer in the SF Bay Area.
WinMTR from a problematic game this evening:
| WinMTR statistics |
Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
---|---|---|---|---|---|---|
router.asus. com - 0 | 368 | 368 | 0 | 1 | 19 | 1 |
76-14-x-x.sf-cable.astound. net - 0 | 367 | 367 | 12 | 25 | 115 | 29 |
agg1-sanmat-b-be-5.bb.as11404. net - 0 | 367 | 367 | 8 | 22 | 41 | 25 |
br2-sanmat-ae-2.bb.as11404. net - 0 | 367 | 367 | 4 | 22 | 55 | 30 |
192.175.29.44 - 0 | 367 | 367 | 10 | 21 | 96 | 31 |
cr1-529bryant-be-2.bb.as11404. net - 0 | 368 | 368 | 5 | 21 | 50 | 16 |
eqix-sv8.attblizzard. com - 17 | 224 | 188 | 8 | 22 | 48 | 23 |
ae1-br01-eqsv5.as57976. net - 0 | 368 | 368 | 7 | 23 | 226 | 22 |
xe-0-0-1-1-br02-eqla1.as57976. net - 1 | 353 | 350 | 14 | 62 | 2860 | 49 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
No response from host - 100 | 74 | 0 | 0 | 0 | 0 | 0 |
Thanks for your efforts looking into this.
PACKET LOSS and LATENCY SPIKES STILL PRESENT
All HW (Router/modem/PC) rebooted and DNS cache flushed to eliminate that.
I have the same issues as always. Present in QP and able to recreate in Training as previously.
NOTE: ALL CONNECTIONS ARE CONTINUOUS TO LAX1 UNTIL I MANUALLY DISCONNECT.
ALL INBOUND LOSS is apparent from beginning of established connection till the end (QP/Training/Arcade)
Same with good connections, they are good from beginning to end. HUGE LATENCY SPIKING going on as well in some.
Normally 40ms to LAX1 for me stable, but with bad sessions the LAT is wild 60-100+ ms on top of the Packet Loss.
.
.
LAX1 24.105.10.162:26579 30-60% INBOUND PACKET LOSS & 60-100ms LAT 9:00-9:05 PM PST ( 5 min in training) 01-02-19
LAX1 24.105.15.228:26536 NO PROBLEMS 9:05-9:10 PM PST ( 5 min in training) 01-02-19
LAX1 24.105.15.228:26532 NO PROBLEMS 9:10-9:15 PM PST ( 5 min in training) 01-02-19
LAX1 24.105.15.228:26554 8-22% INBOUND PACKET LOSS 9:15-9:20 PM PST ( 5 min in training) 01-02-19
LAX1 24.105.15.228:26544 NO PROBLEMS 9:20-9:25 PM PST ( 5 min in training) 01-02-19
.
.
.
Looking Glass while connected to LAX1:
TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
1 Blizzard Blizzard 2.551 ms 2.543 ms 2.546 ms Blizzard(24.105.18.2) 2.461 ms 2.499 ms 2.503 ms
3 137.221.105.14 (137.221.105.14) 2.562 ms 2.583 ms 2.595 ms
4 137.221.66.22 (137.221.66.22) 2.557 ms 2.560 ms 2.574 ms
5 137.221.83.68 (137.221.83.68) 13.168 ms 13.173 ms 16.084 ms
6 137.221.65.68 (137.221.65.68) 13.122 ms 20.672 ms 20.678 ms
7 137.221.65.1 (137.221.65.1) 13.452 ms 30.303 ms 30.339 ms
8 137.221.65.7 (137.221.65.7) 12.666 ms 15.077 ms 15.071 ms
9 137.221.70.32 (137.221.70.32) 13.072 ms 13.086 ms 13.164 ms
10 cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182) 13.262 ms 12.853 ms 12.737 ms
11 cr1-che-b-hu-0-7-0-21-0.bb.as11404.net (192.175.28.109) 14.950 ms 14.669 ms 14.958 ms
12 * * *
13 * * *
14 * * *
15 * * *
03/01/2019 05:27:33 UTC
--------------------
TRACEROUTE:
traceroute to 76.14.108.x (76.14.108.x), 15 hops max, 60 byte packets
1 Blizzard Blizzard 1.749 ms 7.054 ms 7.051 ms Blizzard(24.105.18.2) 7.004 ms 7.020 ms 7.022 ms
3 137.221.105.14 (137.221.105.14) 7.044 ms 7.060 ms 7.064 ms
4 137.221.66.22 (137.221.66.22) 7.022 ms 7.078 ms 7.080 ms
5 137.221.83.68 (137.221.83.68) 14.989 ms 15.008 ms 15.031 ms
6 137.221.65.68 (137.221.65.68) 14.894 ms 13.198 ms 13.195 ms
7 137.221.65.1 (137.221.65.1) 13.444 ms 13.443 ms 13.428 ms
8 137.221.65.7 (137.221.65.7) 13.996 ms 13.966 ms 13.442 ms
9 137.221.70.32 (137.221.70.32) 13.404 ms 12.950 ms 13.074 ms
10 cr1-sjo-p200.bb.spectrumnet.us (206.223.116.182) 13.255 ms 13.196 ms 13.416 ms
11 cr1-che-b-hu-0-7-0-21-0.bb.as11404.net (192.175.28.109) 15.156 ms 15.351 ms 14.681 ms
12 174.127.183.33 (174.127.183.33) 15.915 ms 15.387 ms *
13 * * *
14 * * *
15 * * *
03/01/2019 05:27:33 UTC
--------------------
MTR:
Start: Thu Jan 3 05:27:33 2019 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.5 0.9 0.0
3.|-- 137.221.105.14 0.0% 10 1.0 0.7 0.5 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.9 0.5 2.8 0.7
5.|-- 137.221.83.68 0.0% 10 12.9 16.4 12.7 33.2 7.6
6.|-- 137.221.65.68 0.0% 10 12.9 17.9 12.8 39.3 9.5
7.|-- 137.221.65.1 0.0% 10 12.8 14.7 12.8 29.5 5.2
8.|-- 137.221.65.7 0.0% 10 35.0 19.6 12.8 57.6 15.1
9.|-- 137.221.70.32 0.0% 10 13.1 12.7 12.6 13.1 0.0
10.|-- cr1-sjo-p200.bb.spectrumnet.us 0.0% 10 13.1 12.9 12.7 13.1 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.0 0.0
12.|-- 174.127.183.33 30.0% 10 15.4 20.8 15.2 50.5 13.1
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
03/01/2019 05:27:33 UTC
--------------------
MTR:
Start: Thu Jan 3 05:27:33 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0 Blizzard 0.0% 10 0.9 0.6 0.5 0.9 0.0
3.|-- 137.221.105.14 0.0% 10 0.8 0.7 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 4.6 1.1 0.5 4.6 1.2
5.|-- 137.221.83.68 0.0% 10 13.0 14.8 12.7 32.3 6.1
6.|-- 137.221.65.68 0.0% 10 12.8 15.8 12.8 41.8 9.1
7.|-- 137.221.65.1 0.0% 10 12.9 13.1 12.7 14.4 0.3
8.|-- 137.221.65.7 0.0% 10 20.5 16.3 12.6 39.9 8.6
9.|-- 137.221.70.32 0.0% 10 12.7 12.7 12.6 13.2 0.0
10.|-- cr1-sjo-p200.bb.spectrumnet.us 0.0% 10 13.1 12.9 12.6 13.1 0.0
11.|-- cr1-che-b-hu-0-7-0-21-0.bb.as11404.net 0.0% 10 14.8 14.8 14.6 15.0 0.0
12.|-- 174.127.183.33 70.0% 10 15.6 15.7 15.6 15.8 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
03/01/2019 05:27:33 UTC
--------------------
.
.
.
WinMTR While connected in Training to LAX1 24.105.15.228:
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.x.x - 0 | 129 | 129 | 0 | 0 | 1 | 0 |
| 76.14.104.1 - 0 | 129 | 129 | 8 | 15 | 42 | 17 |
| 174.127.183.24 - 0 | 129 | 129 | 9 | 15 | 56 | 17 |
| 192.175.28.107 - 0 | 129 | 129 | 6 | 17 | 55 | 20 |
| 206.197.187.42 - 1 | 125 | 124 | 11 | 18 | 47 | 26 |
| 137.221.70.33 - 1 | 125 | 124 | 11 | 21 | 66 | 24 |
| 137.221.65.6 - 1 | 125 | 124 | 19 | 50 | 956 | 22 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider