| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.routerlogin.com - 0 | 227 | 227 | 0 | 0 | 14 | 0 |
| 4.216-158-243-unused.kitcarson.net - 0 | 227 | 227 | 0 | 1 | 13 | 0 |
| 186.216-158-240-unused.kitcarson.net - 0 | 227 | 227 | 7 | 7 | 24 | 7 |
| xe-1-2-1.cr01.abq.as7850.net - 1 | 220 | 218 | 7 | 9 | 76 | 7 |
| cr02-cr01.et-2-0-0.cr02.abq.as7850.net - 0 | 227 | 227 | 7 | 8 | 21 | 7 |
| lax-abq.xe-2-3-1.cr01.lax.as7850.net - 0 | 227 | 227 | 27 | 28 | 36 | 28 |
|be-103-pe02.losangeles.ca.ibone.comcast.net - 17 | 138 | 115 | 0 | 40 | 49 | 40 |
|be-2102-cs01.losangeles.ca.ibone.comcast.net - 20 | 130 | 105 | 40 | 41 | 50 | 41 |
|be-2112-pe12.losangeles.ca.ibone.comcast.net - 20 | 130 | 104 | 39 | 40 | 51 | 40 |
|as12989-1-c.600wseventh.ca.ibone.comcast.net - 0 | 227 | 227 | 28 | 32 | 133 | 28 |
| ae1-br01-csla1.as57976.net - 0 | 227 | 227 | 73 | 92 | 1243 | 73 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| 137.221.65.133 - 0 | 227 | 227 | 82 | 407 | 1228 | 317 |
| et-0-0-0-pe04-eqch2.as57976.net - 1 | 223 | 222 | 72 | 76 | 141 | 82 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 46 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderIt was fine the first 2 dungeons we ran, then the third one went through the roof. Same group all guilides
Can you be more specific about “serious lag”? How high of a ping are you’re seeing? In the test, the ping inside Comcast’s network is already 133ms before connecting to Blizzard or their routing peers.
That hop is blizzard owned. That hop looks to be having some issues…
Best 82ms, average 407ms, worst 1228ms
I usually run about 70ms. Last night it was 1200. This is not the first time it happened. Its like rolling the dice on what latency I am going to get when I join an instance.
Here is what it is running now. It’s a little higher than normal. 85 - 90 ms.
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| www.routerlogin.com - 0 | 433 | 433 | 0 | 0 | 9 | 0 |
| 4.216-158-243-unused.kitcarson.net - 0 | 433 | 433 | 0 | 1 | 16 | 1 |
| 186.216-158-240-unused.kitcarson.net - 0 | 433 | 433 | 7 | 7 | 27 | 7 |
| xe-1-2-1.cr01.abq.as7850.net - 0 | 433 | 433 | 7 | 9 | 68 | 7 |
| cr02-cr01.et-2-0-0.cr02.abq.as7850.net - 0 | 433 | 433 | 7 | 7 | 20 | 7 |
| lax-abq.xe-2-3-1.cr01.lax.as7850.net - 0 | 433 | 433 | 27 | 28 | 41 | 28 |
|be-103-pe02.losangeles.ca.ibone.comcast.net - 0 | 433 | 433 | 39 | 39 | 52 | 39 |
|be-2102-cs01.losangeles.ca.ibone.comcast.net - 1 | 430 | 429 | 38 | 38 | 52 | 38 |
|be-2112-pe12.losangeles.ca.ibone.comcast.net - 0 | 433 | 433 | 39 | 39 | 54 | 39 |
|as12989-1-c.600wseventh.ca.ibone.comcast.net - 0 | 433 | 433 | 28 | 32 | 95 | 28 |
| ae1-br01-csla1.as57976.net - 0 | 433 | 433 | 73 | 78 | 209 | 74 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe04-eqch2.as57976.net - 0 | 433 | 433 | 72 | 75 | 200 | 73 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 87 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud ProviderSeveral of the Blizzard owned edge routers apply ICMP filtering policies which will cause connection test packets (ICMP) to take longer to respond. This can make it look like the device is having issues when infact it’s performing well and processing all game traffic (TCP packets) without a problem. So it’s important to look at the entire path to get the overall picture.
@Borlok - The latest WinMTR doesn’t seem to show any issues that would be causing high latency spikes up to 1200ms like you’re describing. The last hop in the test et-0-0-0-pe04-eqch2.as57976.net is pinging around 75ms average, so if you’re seeing 85-90ms in-game the extra latency there may just be due to client/server processing that gets added on top of the base latency.
If you can run the WinMTR in the background while playing during the evening/night and capture what’s happening as the latency spikes up to 1000+ that should give us a better picture. Try to run the WinMTR for at least 10 minutes, and if the problem doesn’t occur after 10 minutes stop and restart the test.
For Thunderhorn realm since it’s US Central use: 24.105.62.129
See explanation above^
There are quite a few posts calling out that specific ip.
If that hop is that overloaded that icmp is deprioritized that much, time to turn up another link or reroute or something.
It has always deprioritized ICMP requests. That’s their DDoS protection they’ve had for years and years.
You say it like they have ICMP turned off. It is not. Turning it OFF would be ddos protection.
The more ICMP is deprioritized, the harder the device is working (under load).
Back to basics man
Thanks for sharing, but deprioritizing ICMP requests is a form of flood protection.