Partial packet loss midway through the hops is normally an ISP issue, and may require contacting an ISP. ![]() 100% packet loss on the first, second, or third hop is normally an indication of a firewall, antivirus program or router blocking internet access. ![]() 100% packet loss is an information stoppage. Packet loss is an indication of information being lost along the way. The middle hops are normally your ISP and transfer locations, and the last few hops are your destination, in this case our servers. The first few hops are local, hop #1 normally being your computer, and #2 normally being your router or modem. Each 'hop" (numbered on the left hand side) represents a location your data is traveling through. The Pingplotter report shows where your information is being sent through the internet (via ICMP packets), and what is happening along the way. It uses a combination of traceroute, ping, and WHOIS to collect data quickly, and then allows you to continue to collect data over time. PingPlotter is a network troubleshooting and diagnostic tool. PingPlotter helps you pinpoint where the problems are in an intuitive graphical way, and to continue monitoring your connection long-term to further identify issues. To find out if you are having connectivity issues, we recommend using PingPlotter. That can be done with both IPV4 and IPV6 DNS addresses.It is a tool to help us determine if your connection speed is the root of your issue. That keeps the ping test within the Rogers system, avoiding any border crossing issues. That works very well.Ī secondary target for latency detection purposes is the Rogers DNS. You can use the CMTS as a target for packet loss detection in the external cable system. Since firmware version 2.0.10.27, there has been a modem timing issue that causes high ping spikes for any ping test to the CMTS. Note for the white CODA-4582 modem, you can't run a ping test to the CMTS for the purpose of latency observation / detection. The bottom plot averages out, looking better and better as you lose those high latency spikes, but, the top data MAX column will show the true high latency point in the displayed plot area assuming that the FOCUS (Time) is set to Auto.Īny time you see packet loss indicated from the modem or CMTS, when your target is beyond the CMTS, that packet loss is most likely a false loss indication and should be confirmed by running a command line ping test. As you scale up in time period, from 60 seconds, to 10 min, to 24, 48 hours, you cram more and more data into a fixed horizontal plot area. We have a guide on running a ping and traceroute test when you feel your website is running slow. You can try out the PingPlotter application to help pinpoint any problems with network connectivity. Keeping this on Auto simplifies the whole "matching time period" issue. If you’re on a Windows machine, and your website appears to be running slow. If the Focus (Time) is on Auto, then the top data time period matches the bottom plot time period. The ERR column is the packet loss count, ie: the individual packet loss events that occurred in the top data time period. The MAX column is the maximum latency observed in the top data time period. Typically you're interested in the maximum latency, so, right click on the top title bar for the columns, select MAX and ERR for display and drag those two columns to the right to sit beside the MIN column. So, you can have two or more data points at the same horizontal pixel and pingplotter averages that data instead of maintaining the minimum and maximum data points. That happens when there is more data in the plot area than can be displayed as a single pixel point. ![]() Pingplotter unfortunately averages the plotted results. You can also adjust the scaling for the plot to automatic or manual selection to maximize the height of the plotted results. Or in other words, use all of the available area to display the plot area. Drag the bottom plot area up so that the top of the plot display sits just under the text data above it. You will end up with the CMTS as the displayed target in the bottom plot area and should only see packet loss (false loss) indicated from the modem in the upper latency display. Running 0.02 seconds for a ping interval, start the test using that Hop #2 address. Stop the test, right click on the IP address for copy the IP address and paste that into the address bar. The CMTS latency doesn't look bad, the packet loss is a false packet loss indication. What modem do you have? If its a CGN3xxx modem, the exact model can be seen at the back of the modem, on the product sticker. "So what are we looking at here?" Pingplotter and Hitron modems don't play well together.
0 Comments
Leave a Reply. |