Packet loss during the night at Baton Rouge, LA

Tested this morning, the packet loss reduced from 5% to 1~2%

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 487 | 487 | 0 | 0 | 0 | 0 |
| 10.131.136.1 - 1 | 483 | 480 | 5 | 7 | 23 | 8 |
| 24.248.104.88 - 2 | 476 | 471 | 6 | 8 | 21 | 8 |
| 70.169.88.34 - 2 | 469 | 462 | 6 | 8 | 45 | 9 |
| dalsbprj02-ae2.0.rd.dl.cox.net - 2 | 472 | 467 | 16 | 20 | 115 | 17 |
| 74.125.52.228 - 1 | 478 | 475 | 15 | 17 | 35 | 17 |
| No response from host - 100 | 99 | 0 | 0 | 0 | 0 | 0 |
| 108.170.229.229 - 2 | 466 | 460 | 15 | 17 | 33 | 17 |
| dfw06s46-in-f4.1e100.net - 2 | 469 | 464 | 15 | 17 | 33 | 17 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

packet loss rise again at night

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 493 | 493 | 0 | 0 | 19 | 0 |
| 10.131.136.1 - 8 | 383 | 355 | 6 | 9 | 44 | 8 |
| 24.248.104.88 - 7 | 392 | 366 | 6 | 10 | 39 | 8 |
| 70.169.88.34 - 7 | 393 | 367 | 6 | 9 | 34 | 12 |
| dalsbprj02-ae2.0.rd.dl.cox.net - 9 | 370 | 339 | 16 | 21 | 125 | 17 |
| 74.125.52.228 - 7 | 391 | 365 | 16 | 20 | 76 | 21 |
| 108.170.252.129 - 7 | 394 | 369 | 16 | 19 | 49 | 18 |
| 108.170.231.71 - 9 | 374 | 344 | 16 | 20 | 76 | 21 |
| dfw28s02-in-f4.1e100.net - 8 | 384 | 356 | 16 | 18 | 47 | 18 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

It appears that the packet loss is starting after the router's hand off to the modem and continuing past that point. With it being a Gateway modem/router there are not many options in testing it besides trying a different Gateway or standalone modem to rule out what is causing the loss.

---

Hi Edward,

This problem is weird because it only happens at night. One of my friends who lives in the same apartment community has exactly the same issue with cox. Do you think the reason is node saturation in this area? The zip code is 70820-8821.

Thanks.

Hello,

We were able to test for node utilization and at no point does the node reach a max capacity.  With it only occurring at what would be considered "peak" times for gamers.  It's felt the issue is going to be with the sites ingestion server.  Something you can try is run the ping plotter in the day when no issues are found and compare them to the times issues are evident.  If the same routes are used this would further point to that server.  Another thing to try is running routes to other game sites to see if you see same results. 

Hi DannyS,

I have replaced my old gateway modem with a brand new gateway modem from cox (cox only offers gateway for rent). I have tested it for few days. The packet loss is reduced but the problem still exists.

I don't think the problem is the game server because the host for all the tests I have done is google. Also, my friend (I mentioned above) plays a different game but he has the same issue. 

Here is the most recent test:

Hello,

If this issue returns tonight.  Can you run a test somewhere else to compare.  There is some loss off the gateway, but another spike does shows up on Google's hops in that route.  If you achieve the same results.  We at that point would need to offer a tech to come out for more testing.  As they have ability so test for some things we do not have access to.  If needed please let us know on Twitter at @CoxHelp, visit us on Facebook, or email by at cox.help@cox.com along with a copy of this thread, if you need a tech to come out.  We can provide you available times there.

Hi DannyS,

Thank you for your reply. This problem still exists. I ask my friend who lives in the same apartment community to test it. My friend moved here and had cox installation at the beginning of July this year. As for asking for a tech, I am afraid the time is too late for a tech because this problem only shows up at night.

Here is the ping plotter results from my friend:

Here is my test using cox.com:

Hello,

If still having issues at night connecting to a particular site.  Can you send a tracert to that site, both during the day when you have no issues connecting and another at night.  This way we can compare routes side by side.  This will help determine if this issue is truly on our network or not. 

Hi Danny,

I am still having this problem every night. As for the packet loss, sometimes it is better, sometimes it is worse.

Here are pingplotter results:

This test is for google during daytime:

This is for google at night:

This is for the game server during daytime:

This is for the game server at night:

Please ignore the time shown in pingplotter, the time display of my computer is messed up.

Hey Jerryy,

Based on your zip code, I live close to you, more than likely a complex or two over. I'm having pretty much the exact same issue connecting to play at night around 7pm, it even recurs later in the evening sometimes as well. I've had to restart my modem at least three times a week for the past three months and sometimes that doesn't even help. I have a theory that it is node saturation, however I don't think there's anything we can do about that. Have you had any luck in fixing the issue?