Help me read this MTR. Rubber banding like crazy.

Technical Support
Hi Guys --

Cable guy came to the house today, checked all connections, made sure all signals were good, and didn't correlate that you can still have great bandwidth with terrible latency.

Can someone confirm my suspicions? Looking at this it appears I have rough;y 30% packet loss at some node called lag-133.

Is that my ISP? Is that Blizz? Is that just someone in between?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.10.1 - 0 | 210 | 210 | 0 | 0 | 1 | 0 |
| 10.112.6.1 - 0 | 210 | 210 | 8 | 11 | 20 | 11 |
| 192.168.22.129 - 0 | 210 | 210 | 8 | 13 | 25 | 13 |
| 10.224.252.221 - 0 | 210 | 210 | 20 | 23 | 52 | 24 |
| lag-133.ear1.Dallas1.Level3.net - 26 | 93 | 69 | 0 | 795 | 3798 | 21 |
| No response from host - 100 | 42 | 0 | 0 | 0 | 0 | 0 |
| BLIZZARD-EN.ear3.Dallas1.Level3.net - 0 | 210 | 210 | 21 | 26 | 44 | 27 |
| ae1-br01-eqda6.as57976.net - 6 | 170 | 160 | 51 | 55 | 114 | 53 |
| et-0-0-2-br02-swlv10.as57976.net - 0 | 210 | 210 | 52 | 57 | 152 | 58 |
| et-0-0-29-br01-eqam1.as57976.net - 0 | 210 | 210 | 51 | 57 | 96 | 56 |
| et-0-0-2-br01-eqla1.as57976.net - 0 | 210 | 210 | 50 | 58 | 186 | 54 |
| be1-pe01-eqla1.as57976.net - 4 | 186 | 180 | 51 | 53 | 63 | 52 |
| 24.105.30.129 - 3 | 194 | 189 | 52 | 54 | 65 | 55 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Bump. Is there not enough information here?
that is the first pop off of your private networks. Contact your isp/networking support team
Howdy RightMeow,

Looking over the MTR I see you are running through a nod that is currently having issues: | lag-133.ear1.Dallas1.Level3.net - 26 | 93 | 69 | 0 | 795 | 3798 | 21 |

We are gather information on this and looking into the best way to get this fixed. Right now the only work around we have found is trying with a vpn if you feel comfortable setting one up.

Hopefully this will be fixed soon so you can get back to playing!
Also having issues with Diablo and Overwatch. On nextlink Just outside of DFW.

Tracing route to 24.105.30.129 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.88.1
2 9 ms 6 ms 4 ms 100.72.8.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 8 ms 8 ms 7 ms pr01-eqfr5.blizzardonline.net [206.53.202.43]
7 * * * Request timed out.
8 504 ms 478 ms 502 ms et-0-0-2-br02-swlv10.as57976.net [137.221.65.67]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 45 ms 44 ms 42 ms 24.105.30.129

Trace complete.
12/05/2018 06:35 PMPosted by Joynueer
Howdy RightMeow,

Looking over the MTR I see you are running through a nod that is currently having issues: | lag-133.ear1.Dallas1.Level3.net - 26 | 93 | 69 | 0 | 795 | 3798 | 21 |

We are gather information on this and looking into the best way to get this fixed. Right now the only work around we have found is trying with a vpn if you feel comfortable setting one up.

Hopefully this will be fixed soon so you can get back to playing!


Similar to my issues. Interesting that if I swap over and use AT&T to get out of the Dfw metroplex, there is no issues.

Over AT&T

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| wrt3200_1.lan - 0 | 119 | 119 | 0 | 0 | 0 | 0 |
| 172.20.10.1 - 0 | 119 | 119 | 1 | 3 | 12 | 2 |
| 172.26.96.169 - 0 | 119 | 119 | 23 | 43 | 105 | 36 |
| 172.16.68.252 - 0 | 119 | 119 | 29 | 44 | 102 | 30 |
| No response from host - 100 | 23 | 0 | 0 | 0 | 0 | 0 |
| 12.83.179.194 - 0 | 119 | 119 | 32 | 51 | 101 | 44 |
| 12.122.100.105 - 0 | 119 | 119 | 34 | 48 | 97 | 34 |
| 12.244.90.238 - 0 | 119 | 119 | 30 | 48 | 86 | 36 |
| ae1-br01-eqda6.as57976.net - 0 | 119 | 119 | 58 | 79 | 114 | 69 |
| et-0-0-2-br02-swlv10.as57976.net - 0 | 119 | 119 | 59 | 80 | 191 | 65 |
| et-0-0-29-br01-eqam1.as57976.net - 0 | 119 | 119 | 61 | 79 | 199 | 65 |
| et-0-0-2-br01-eqla1.as57976.net - 0 | 119 | 119 | 57 | 74 | 138 | 58 |
| be1-pe02-eqla1.as57976.net - 0 | 119 | 119 | 60 | 76 | 120 | 67 |
| 24.105.30.129 - 0 | 119 | 119 | 56 | 74 | 104 | 65 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

and over grande via the Equinix exchange in dallas:

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

| WinMTR statistics |

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

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

| wrt3200_1.lan - 0 | 284 | 284 | 0 | 0 | 4 | 0 |

| 192.168.0.1 - 99 | 58 | 1 | 2 | 2 | 2 | 2 |

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

| ae2-188.aggr01.fscotx.grandecom.net - 0 | 284 | 284 | 8 | 13 | 54 | 14 |

| ae4-0.core01.gf01.dllstx.grandecom.net - 0 | 284 | 284 | 9 | 13 | 49 | 10 |

| eqix-da1.blizzard.com - 0 | 284 | 284 | 10 | 14 | 43 | 12 |

| ae1-br01-eqda6.as57976.net - 12 | 192 | 169 | 0 | 44 | 82 | 40 |

| et-0-0-2-br02-swlv10.as57976.net - 0 | 284 | 284 | 40 | 46 | 114 | 43 |

| et-0-0-29-br01-eqam1.as57976.net - 1 | 272 | 270 | 40 | 74 | 3079 | 41 |

| et-0-0-2-br01-eqla1.as57976.net - 4 | 247 | 238 | 39 | 79 | 1941 | 42 |

| be1-pe01-eqla1.as57976.net - 5 | 244 | 234 | 40 | 42 | 50 | 43 |

| lax-eqla1-ia-bons-02.as57976.net - 5 | 240 | 229 | 40 | 43 | 53 | 44 |

| 24.105.30.129 - 4 | 248 | 239 | 39 | 41 | 50 | 39 |

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

Currently working around by hoping a VPN to Chicago, and into 24.105 from there.
12/05/2018 06:35 PMPosted by Joynueer
Howdy RightMeow,

Looking over the MTR I see you are running through a nod that is currently having issues: | lag-133.ear1.Dallas1.Level3.net - 26 | 93 | 69 | 0 | 795 | 3798 | 21 |

We are gather information on this and looking into the best way to get this fixed. Right now the only work around we have found is trying with a vpn if you feel comfortable setting one up.

Hopefully this will be fixed soon so you can get back to playing!


When you say VPN you mean get an additional service or is there some magic I don’t know about.

Currently I am not subscribed to any VPN services. Apparently the route to this node is impacting a lot of people. I use Cableone as my ISP and those who have Charter as their ISP in my area are not experiencing issues.
you need somewhere that is not experiencing problems, that you can get to.

Then you tunnel to their site (much like work vpn's).

That way your traffic goes
Home->yourISP->vpnEndpoint->blizzard

It takes some network understanding etc. And its a work around only. Blizzard and their ISP needs to get it resolved.
| lag-133.ear1.Dallas1.Level3.net - 26 | 93 | 69 | 0 | 795 | 3798 | 21 |


I see this was not explained. This hop is Level 3 Communications who is a major backbone traffic handling company. They are not Blizzard's ISP. Blizz can work with other companies to ask them to fix things, but Blizz can't MAKE them do it because Blizz is not their customer and is not paying them.

12/06/2018 09:55 PMPosted by RightMeow
When you say VPN you mean get an additional service or is there some magic I don’t know about.

Home > Your ISP > Backbone service > Blizzard <----- Now
Home->yourISP->vpnEndpoint->blizzard <---- Close enough although I would not quite put it that way :)

A VPN is a detour for your data so that it takes a different "road" to the Blizzard endpoint you want. Just like a detour on a different road around a construction point.

Yes, it is an additional service. Sometimes you can get the same result by tethering to a phone so that you go through a completely different route.
Blizzards vendor (ISP) is one of the backbone service's customers. The problems all occur at or very near to Blizzard MW's. The problems from the exchange in Dallas I can see all seem to only have to do with routes towards blizzard servers, not to other major companies also similarly served from the same hop (exchange) in DFW.

Blizzard/Activision's vendor (ISP) is not delivering traffic to them properly, and they should be working / pressuring their ISP to work with and pressure its vendor (the backbone) as to why it is not reliably delivering traffice to them.

Blizzard is a far bigger customer than individuals, and they pay a premium price for reliable and dependable delivery. I have taken part in some of these customer/ISP/backbone diags. It takes a big player with reproducible issues to push via their ISP. I'm glad at least that Blizzard is pursuing that somewhat.

I just don't get why the effort to push back on those asking for the same. This all started in proximity to blizzard MW's. Surely Blizzard and their ISP are reviewing any and all changes that might have been part of those?
12/07/2018 11:29 AMPosted by Mutt
Blizzards vendor (ISP) is one of the backbone service's customers.


This is also true as far as I know.

12/07/2018 11:29 AMPosted by Mutt
Surely Blizzard and their ISP are reviewing any and all changes that might have been part of those?


Yes.

They also recently put up a thread over on the WoW TS forum asking for the kind of player data you guys posted here. https://us.forums.blizzard.com/en/wow/t/data-gathering-for-connection-issues-when-routed-through-dallas-region-dec-7/40550?fbclid=IwAR3PzQO2JAPF2nhkur2uOUN1ORyqzF0lvKEZ2IahqBZp6mEwQXGDMcVn1nY

There tend to be more players there so it is just a means to get more network reports.
This happens in WOW and can provide the same data there too!
RightMeow

It's happening in almost all our games. It is a routing issue that is currently under investigation on multiple fronts. It's affecting multiple different ISP's in multiple different locations.

We have a WoW thread Here and an Overwatch thread Here.

The moment we hear of any news, we will provide updates.

Join the Conversation

Return to Forum