Some basic information for the SmokePing tool:
The status at August 2014 is that there are three smoke ping servers running. The one in California had a couple of different issues recently and these have been corrected.
What does SmokePing do?
SmokePing generates graphs that can reveal the quality (packet loss and latency variability) & reachability of your IP address from several geographically distributed locations.
What hosts will ping me?
The smoke ping servers, and their IPs, are listed at the bottom of the results page.
Why is low jitter and zero packet loss important?
Communications over the internet are built with layers of increasing complexity, and one of the lowest layers is how quickly and reliably IP data packets are transmitted and received. If this layer performs poorly then everything else is affected: Speed drops, web pages mysteriously hang, programs disconnect, audio video and voice quality suffers and so on.
Ok I'm sold, what do I do?
If you want to do a quick check of the quality of an IP address, then simply elect to have smokeping monitor it closely for 24 hours, (or more, if you are a registered user of the site).
The main result page for an IP you are monitoring shows an overview graph for each monitoring station. At the moment, there are three stations. The red line on the graph represents the average ping time over the time period. The graphs scroll to the left, with new data appearing on the right.
If you click any individual monitoring station (click the graph or the navigation links to the left), you are able to see the ping plot in more detail. In particular, the color of the line segments (color key at the bottom of the graph) indicates overall packet loss. "Smoke" indicates variability of latency (ping time) at that instant. The more variability, the more "smoke" that appears around the colored line segment.
Because our implementation of SmokePing uses large ping packet sizes, and each data point on the graph is not just a single measurement, but many pings, the graph is more sensitive than normal ping plotting programs and will uncover latency variability or loss that may only show up when the line is under fairly heavy use.
The three monitoring stations are independent from each other so they will also confirm a problem as yours if they all show the same suspicious data (excessive smoke, a rise in average ping time or actual packet loss) at the same time. If just ONE out of three monitoring stations shows a problem, then you can discount it.
What should I hope to see?
Here is an example of a nice stable connection NEAR to a monitoring station. Although there is "smoke," there is no packet loss, and the smoke is only +/- a few milliseconds. (Click thumbnail for full size.)
Here is an example of the same connection from the other side of the country. Notice that since the ping time is much higher, the variability (smoke) is almost invisible. (Click thumbnail for full size.)
(Screenshots of different kinds of bad connections will be posted here soon.)
When viewing the results, please keep in mind that your IP may be very near to one of the stations and much further away from the other two. The graphs auto-scale, so "smoke" shown on an X scale composed of just a few ms top to bottom is far less interesting than smoke shown on a scale of 100ms! Packet loss, (line segments that are not green) on any scale, is always interesting!
You can also visit the SmokePing home page where there is another description of how to interpret SmokePing data: reading smokeping graphs.
Feedback received on this FAQ entry:
I have pinging enabled, or I have pinging enabled only for dslreports. Line quality tests ping OK but the Smokeping test fails. What is the IP address of the smokeping server?
• ny-monitor.dslreports.com - 18.104.22.168
• dslreports-west2.speakeasy.net - 22.214.171.124 and 126.96.36.199
• dslreports2-west.megapath.net - 188.8.131.52
Recommend putting these into your rules by IP address.
Smokeping may do an initial reachability call-out from mail.dslreports.com (184.108.40.206) so it is also recommended to add a rule for that IP address.
Feedback received on this FAQ entry: