Excessively High Ping, Jitter, Intermittent packet loss, connection almost useless between 6-11pm

3:30-4:15pm PST
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                                      Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|  --------------------------------------------------|----|---------|---------|------|------|-------|------|
|                                             192.168.0.1 -   0 | 1982 | 1982 |     0 |     0 |     1   |   0 |
|                                             10.38.180.1 -   1 | 1911 | 1893 |      3 |   20 |  348 |   9 |
|                                      100.127.73.152 -   2 | 1883 | 1858  |    3 |   22 |  349 |   8 |
|                                        100.120.100.6 -   1 | 1911 | 1893 |     5 |   22 |  347 |    7 |
| mtc3dsrj01-ge708.103.rd.ok.cox.net -   1 | 1911 | 1893 |   52 |   69 |  397 |  55 |
|           ip70-167-150-222.at.at.cox.net -   1 | 1911 | 1893 |   50 |   66 |  393 |  55 |
|                     No response from host - 100 |   397 |        0 |     0 |     0 |      0 |     0 |
 
The final hop is Riot Games in Chicago, as per normal game servers deny ping requests.

Here is another tracert to google.com
|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                            Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------  ------------------------|------|------|------|------|--------|-------|
|                               192.168.0.1 -     0 |   59 |   59 |      0 |     0 |        1 |      0 |
|                               10.38.180.1 -     0 |   59 |   59 |      3 |   17 |  264 |    22 |
|                          100.127.73.154 -    0 |   59 |   59 |      3 |   18 |  262 |    22 |
|                          100.120.100.10 -    0 |   59 |   59 |      5 |   20 |  265 |    23 |
|                                  68.1.4.252 -     0 |   59 |   59 |    15 |   32 |  276 |    31 |
|                            68.105.30.142 -    2 |   55 |   54 |    15 |   26 |    57 |     34 |
|                         108.170.238.58 -    0 |   59 |   59 |     16 |   29 |  271 |    34 |
|                          209.85.245.229 -    2 |   55 |   54 |    16 |   30 |  277 |    33 |
|       lax17s38-in-f14.1e100.net -    0 |   59 |   59 |   15 |   30 |  276 |     33 |

Better Packet loss in a smaller sample size, but equally atrocious ping spikes.

Also of course my Modem isn't showing packet loss at the time of your reply, being 4AM PST and all.... Try looking at your network during 4-11pm when its on fire, vs 4am when most people are sleeping.

I can sit here for the next 8hours collect tracert data showing insane ping spikes and jitter, with intermittent packet loss.  But it isn't going to show anything different, than what is already here, and the same issue everyone else is having.  I will continue to collect data, to provide to the FCC, if the issue is not resolved soon :)

Tracert Data to Discord, which we are using to work from home atm, for both VOIP, and screen share /streaming... it is impossible to use Discord, Slack, and/or Skype at the moment.

Another 1 during peak hours..... Feel free to look into it, and you know ping my modem not at 4am, when the node isn't over saturated.  Either way, I filed a FCC complaint, so Cox will be forced to lie to me and the FCC within the next 30days,about how you oversell nodes,constantly.  Good thing also have BBB, and AZ attorney general to reach out to as well :)