![a good test for pingplotter a good test for pingplotter](https://i.imgur.com/lf4Pcii.png)
If you see more T3 timeouts occurring (remember, check the time, don't just look at it and say "it's only one") you need a Cox tech to check out the equipment in your neighborhood. Because your downstream looks good, this issue could be caused by upstream noise ingress which is a very common problem on the cable network. No amount of Microsoft troubleshooting will resolve a T3 timeout.
![a good test for pingplotter a good test for pingplotter](https://community.netgear.com/ejquo23388/attachments/ejquo23388/Orbi/89555/1/2020-04-21%2012_42_52-PingPlotter%20Pro.png)
Even if you see "only one" check the time and see if it's changed. Keep watching the logs and see if the T3 timeouts continue. This is because the modem only shows the most recent entry for each event type if more than one event occurs in a row. Because of the way the modem logs work, you might see "only one" T3 timeout, but if you refresh that page you'll probably notice that the time of the T3 timeout is changing. Every time a T3 timeout occurs, you will have major packet loss and you often will have some packet loss between T3 timeouts as well. TL DR: Don't waste time with PingPlotter and speed tests until your modem signals and modem logs are clean and correct. Otherwise you're just wasting your time on a problem that those tools can't identify. Once you have good downstream and upstream signals, virtually zero uncorrectable codewords, and clean modem logs with no T3/T4 timeouts, only then should you move on to running PingPlotter and speed tests. When you check the logs, look for CM-STATUS messages (minor issues but if you see them happening more and more often, get ready for bigger problems), dynamic range window violations (minor upstream RF issue but usually indicates that worse problems are coming in the future), T3 timeouts (indicating a bad problem on the upstream RF connection), T4 timeouts (indicating a very bad problem with the whole RF connection), and unexpected modem reboots (usually caused by the modem rebooting to try to re-establish a signal on the RF network). But if any uncorrectable numbers are increasing during the day, you have a problem that PingPlotter and speed tests won't fix. Every now and then you might get a burst of a few thousand uncorrectables overnight when Cox does maintenance. Most times you will need a Cox tech to fix this. That needs to be resolved before you run PingPlotter or speed tests. If you see uncorrected codewords continuously increasing, there is a problem in the RF network. The most important indicator on the downstream signal page is uncorrected codewords. Upstream power being too high is definitely a thing and indicates problems in the RF network. There's basically no such thing as upstream power being too low (unless it's zero) so ignore that. The only bad information I've seen out there are some Arris pages that make people think their upstream power level is too low. If you post cut/paste signals and modem logs people on the forum will often help you understand them. There is information available on many sites about modem signals and most of it is accurate. Trying to troubleshoot an issue without checking the RF network is like building a house without a foundation. The RF network is the foundation of everything. You need to find out how to do this for your individual modem. Most modems will let you check signal levels and event logs by going to the IP address 192.168.100.1 in a browser. Sometimes RF network problems are caused by your equipment or your wiring, but more often these problems are in the Cox network and are outside of your ability to control. Problems in the RF network are very common, and if you don't fix those, results from PingPlotter or speed tests aren't valid. The RF network is the network that runs on the coaxial cable that comes out of the back of your modem. When you're experiencing problems with Cox internet service, you need to check and confirm the reliability of the RF network before you do anything else. How's that for a clickbait headline? But this is really about that headline.