High World Latency to Central Server

Realm: Kel’Thuzad
Time: 3:22PM EST

ran a trace route and found no problems with minimal packet loss (<10/100) with local hops 1-11, 50ms latency average.

12 58ms 4/ 100 = 4% 0/ 100 = 0% et-0-0-2-br01-eqch2.as57976. net [137.221.65.13]
6/ 100 = 6% |
13 50ms 10/ 100 = 10% 0/ 100 = 0% be1-pe02-eqch2.as57976. net [137.221.69.69]
0/ 100 = 0% |
14 — 100/ 100 =100% 90/ 100 = 90% chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
0/ 100 = 0% |
15 56ms 10/ 100 = 10% 0/ 100 = 0% 24.105.62.129

However, 100% packet loss at IP address: 137.221.66.15.

when i looked up the address on google, it is associated with blizzard’s network.

100% packet loss is actually not a problem - the hop just isn’t responding to the test. it is more concerning that there is 4% loss visible starting at hop 12 - we need to see if that starts there or earlier.

can you post a winmtr - run it for 10-15 minutes to the central server and post. https://us.battle.net/support/en/article/27780

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

| WinMTR statistics |

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

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

| router.asus.com- 0 | 1408 | 1408 | 0 | 0 | 9 | 0 |

| ...** - 5 | 1186 | 1130 | 3 | 9 | 46 | 5 |

|***.comcast.net - 5 | 1194 | 1140 | 2 | 10 | 58 | 8 |

| .*.***.*** - 5 | 1190 | 1135 | 5 | 12 | 68 | 8 |

|***.comcast.net - 5 | 1190 | 1135 | 7 | 15 | 52 | 12 |

|***.comcast.net - 5 | 1198 | 1145 | 9 | 17 | 78 | 16 |

|***.comcast.net- 5 | 1190 | 1135 | 24 | 32 | 81 | 32 |

|***.comcast.net - 5 | 1202 | 1150 | 37 | 45 | 78 | 42 |

|***.comcast.net - 5 | 1186 | 1130 | 36 | 44 | 98 | 43 |

|***.comcast.net - 6 | 1174 | 1115 | 36 | 44 | 89 | 45 |

| ***.as57976.net - 5 | 1194 | 1140 | 48 | 58 | 207 | 55 |

| ***.as57976.net - 5 | 1181 | 1126 | 48 | 75 | 2422 | 54 |

| ***.as57976.net - 5 | 1194 | 1140 | 48 | 56 | 104 | 54 |

|***.as57976.net - 5 | 1190 | 1135 | 49 | 57 | 87 | 56 |

| 24.105.62.129 - 5 | 1202 | 1150 | 48 | 56 | 87 | 56 |

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

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Just a FYI you do not need to remove the IP addresses the only ones that have any significant and even then not a lot is the first 3

So your lag is starting on the second hop right after your router. I would start by unplugging your modem and router for a minute and replugging them. Then, if you connect wirelessly I would test by connecting via Ethernet. You can post a new winmtr connected via Ethernet if you want us to see if that looks better. If neither of those fixes it I’d contact your isp, as the issue is either with your router/modem or the first hop outside your house.

First off, thanks for the ideas!

I have xfinity Cable gigabit service. I used to have directv DSL.

I have the ASUS AC2600 Router firmware v3.0.0.4.384 and Netgear CM1000 modem running docsis 3.1 on firmware v3.01.06. Both of which are up-to-date.

I used IP lookup to search the IP address associated with the second hop right after the router. It is associated with comcast/xfinity service. From what I read from the modem status page (192.168.100.1) there is no “IP address” to the modem. There is only a serial number, a MAC address, an installed certificate, and hardware and firmware versions. I also checked the “WAN IP” on the router and it is different from the second hop from the WinMTR statistics. So, the IP address on the second hop HAS to be the initial Comcast/xfinity network server.

I was on the phone today and was incredibly unsuccessful in determining the cause of my packet loss on their server. From what they see on their end (be it very primitive), they said nothing was wrong (even though the event logs on my modem say otherwise).

I get two significant warnings and critical messages on my modem after reboot/startup.

  1. Dynamic Range Window Violation: Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=:::::;CMTS-MAC=28:52:61:28:71:ce;CM-QOS=1.1;CM-VER=3.1
    AND RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW

  2. Resetting the cable modem due to docsDevResetNow: SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=:::::;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1

These warnings were coming up during the problem before as well.

Now, after restarting the router and modem about 4 times, the system has returned to normal. However, I do foresee the problem happening again, just as it did before, out of the blue.

My question, to anybody who is in the field of cable or an IT enthusiast/professional, is: can I have peace of mind in knowing it’s probably not my end that’s the problem and anytime there is packet loss on this first step, that it is Comcast’s network that is having problems and not my own?

My next question to IT people is: should I go back to DSL? I had DSL for years and never had any problem with it whatsoever. Anytime the internet started getting a little slow for my liking I would simply restart the router/modem (after months of not having restarted it) and it would work good as new. Now, with cable, I’m getting fluctuations in reliable service (too much noise on the network and packet loss), even though the speeds (900+ mbps DL and 40+mbps UL) are great for downloading large files. Is it normal to feel like I just sacrificed reliability for faster speeds when switching from DSL to cable?

No you don’t need to think about switching to dsl to get more reliability.

We don’t know whether the cause of the issue is your ISP or not. It is possible its your router, probably poor wifi signal, or your modem, or even your wiring. But even if its a malfunctioning first hop, generally ISP’s are good about fixing local issues. That first hop is located roughly ~in your neighborhood, your local comcast techs would be directly able to get that fixed.

It’s possible that just resetting your equipment fixed the issue. If you want to post another winmtr we can check it out. if it comes back later, it’s possible its an equipment issue. this is why if the issue still persists, sometimes it is a good idea to test connected via ethernet, directly to the modem even. that helps us eliminate wifi and the router as the cause of the problem, and leaves us with just the modem or the isp.