|
| |||||
| Home | Reviews | Tools | Forums | FAQs | Find Service | ISP News | Maps | About |
how-to block ads |
SmokePingUpdates to smokeping Smokeping uses 'fping' which does parallel pings. The original version of fping did not increment the sequence number in packets to the same host. This caused a few network devices to simply ignore most ping packets they received. This has been corrected. (as of October 2010). What hosts will ping me? Currently 74.208.229.54 (US, Kansas), 64.81.79.41 (US, California) and 216.254.95.41 (NY, NY) participate. What does SmokePing do? SmokePing generates graphs that can reveal the quality (packet loss and latency variability) & reachability of your IP address from several distributed locations. Why is low jitter and zero packet loss important? Communications over the internet are built on layers of technology, and one of the lowest and most fundamental layers is how quickly and reliably IP data packets are transmitted and received. If this layer performs poorly then everything else is affected in one way or another: Speed drops, web pages mysteriously hang, programs disconnected unexpectedly, VOIP 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 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.
Smokeping seems to be down at the NYC server. I am not seeing any data collection for 3 sites I am smoking. If smoke ping is working over several days and my dynamic IP address changes, which is often the case with disconnects, does that mean smoke ping will be pinging the wrong IP address? It would make more sense to allow smoke ping of a DNS address. 2011-08-13 10:26:06 I was curious to see exactly where the three servers listed under "What hosts will ping me?" are located. Apparently 74.208.229.54 (US, Kansas) is really in Wayne, PA, not Kansas.
http://cqcounter.com/whois/
74.208.229.54 - Geo Information
IP Address 74.208.229.54
Host u15150124.onlinehome-server.com
Location US US, United States
City Wayne, PA 19087
Organization 1&1 Internet
ISP 1&1 Internet
AS Number AS8560 1&1 Internet AG
Latitude 40°05'48" North
Longitude 75°40'83" West
Distance 7722.84 km (4798.75 miles)
64.81.79.41 - Geo Information
IP Address 64.81.79.41
Host dslreports-west2.speakeasy.net
Location US US, United States
City Fremont, CA 94539
Organization Speakeasy
ISP Speakeasy
AS Number AS23504 Speakeasy, Inc.
Latitude 37°51'55" North
Longitude 121°89'62" West
Distance 10427.96 km (6479.64 miles)
216.254.95.41 - Geo Information
IP Address 216.254.95.41
Host dslr-ny2.dslreports.com
Location US US, United States
City New York, NY 10004
Organization Speakeasy
ISP Speakeasy
AS Number AS18566 Covad Communications Co.
Latitude 40°68'88" North
Longitude 74°02'03" West
Distance 7587.01 km (4714.35 miles)
Thanks for including the tool. As a 'semi-geek' I'd appreciate some input on 'acceptable' Median Ping RTT and Packet Loss.
baumgrenze
Thank you for these tools. Previously I relied on my sales guys telling me our T1 was down and reporting it to Earthlink/Verizon since they don't seem to do anything unless I complain. Now I can send them a daily email with the Smoke Ping report link on how poor their service is. Thank you, thank you, thank you... I'm getting a Page Not Found when trying to view my Smoke Ping Results Page. I can start Smokeping and I can see it is pinging my router from the logs, but trying to view it results in a "404 Not Found" for http://www.dslreports.com/r3/smokeping.cgi. I'm getting a Page Not Found when trying to view my Smoke Ping Results Page. by edited by Mike • ny-monitor.dslreports.com - 217.160.255.49 • dslreports-west2.speakeasy.net - 64.81.79.40 and 64.81.79.41 • dslreports2-west.megapath.net - 66.80.135.19 Recommend putting these into your rules by IP address. Smokeping may do an initial reachability call-out from mail.dslreports.com (209.123.192.187) so it is also recommended to add a rule for that IP address.
The IP address for ny-monitor.dslreports.com is incorrect- 217.160.255.49
A ping to ny-monitor.dslreports.com returns u15150124.onlinehome-server.com (74.208.229.54)
It appears that smokeping is hardwired to 217.160.255.49, which is UNREACHABLE
$ ping 217.160.255.49
PING 217.160.255.49 (217.160.255.49) 56(84) bytes of data.
^C
--- 217.160.255.49 ping statistics ---
36 packets transmitted, 0 received, 100% packet loss, time 35279ms
Please change smokeping so that the NYC location returns data, otherwise this tool has limited utility.
2012-11-17 11:31:35 Smokeping is a great tool that is very useful. But I haven't had results from NY for many months. Perhaps the maintainers should just remove the NY configuration?
| ||||||||
| Monday, 08-Apr 12:34:05 | Terms of Use & Privacy | feedback | contact | Hosting by nac.net - DSL,Hosting & Co-lo over 13.5 years online © 1999-2013 dslreports.com. |