The Network Diagnostic Page

Note: This test may generate warnings in your firewall software about port scans or network attacks originating from 209.68.2.155 - please ignore this and do NOT report this to me or Pair Networks, who hosts this web site. This is normal and harmless - no information is being collected.

When diagnosing network problems, it often helps to get data from outside the problem network, as well as from the inside. Unfortunately, not all users have remote access to a machine that can act as an external testing platform.

This page is meant to help alleviate that problem by providing some basic diagnostic information from an outside point.

Diagnostics

Where am I coming from?

This is the ip address of the machine originating the request for this page. This may be the machine you are working on, or it may be a proxy cache elsewhere on the network.

You are connecting from: 38.103.63.16

The nslookup command will attempt to perform a reverse DNS lookup on your IP address. If reverse lookups don't work properly, you may have trouble with some web sites that rely on this information for authorization (e.g., Microsoft and Netscape when downloading domestic-security versions of their browsers). The name of this webserver is iyaaku.pair.com, so the other name is your end.

Server:		209.68.2.155
Address:	209.68.2.155#53

** server can't find 16.63.103.38.in-addr.arpa: NXDOMAIN

How did I get here?

This is the result of running the traceroute command against the IP address from the previous section. This represents the path that data takes to get FROM this server TO that IP address. This may not always yield useful results -- traceroute is blocked on some networks.

 2  192.168.1.8 (192.168.1.8)  1.273 ms  0.789 ms  0.968 ms
 3  208.30.223.37 (208.30.223.37)  1.737 ms  1.884 ms  0.969 ms
 4  144.232.13.145 (144.232.13.145)  10.872 ms  10.822 ms  10.839 ms
 5  sl-bb21-nyc-15-0.sprintlink.net (144.232.13.2)  12.167 ms  14.239 ms  20.011 ms
 6  sl-bb24-nyc-11-0.sprintlink.net (144.232.13.185)  17.009 ms  10.999 ms  11.820 ms
 7  144.232.18.102 (144.232.18.102)  45.895 ms  45.858 ms  52.882 ms
 8  te4-1.mpd01.jfk05.atlas.cogentco.com (154.54.1.153)  46.889 ms  45.579 ms  45.947 ms
 9  te9-2.mpd03.jfk02.atlas.cogentco.com (154.54.5.209)  45.123 ms
    vl3496.mpd03.jfk02.atlas.cogentco.com (154.54.6.49)  45.235 ms
    vl3492.mpd03.jfk02.atlas.cogentco.com (154.54.7.13)  45.526 ms
10  te2-1.ccr02.dca01.atlas.cogentco.com (154.54.6.13)  41.266 ms  39.417 ms
    te9-1.mpd01.dca01.atlas.cogentco.com (154.54.5.253)  43.072 ms
11  te9-4.ccr02.iah01.atlas.cogentco.com (154.54.24.22)  40.083 ms  41.403 ms
    te9-2.ccr02.iah01.atlas.cogentco.com (154.54.24.18)  40.819 ms
12  te3-4.ccr02.lax01.atlas.cogentco.com (154.54.3.186)  73.652 ms
    te4-4.ccr02.lax01.atlas.cogentco.com (66.28.4.238)  73.855 ms
    te4-4.mpd01.lax01.atlas.cogentco.com (154.54.5.102)  74.448 ms
13  te4-1.ccr01.phx02.atlas.cogentco.com (154.54.1.166)  63.442 ms
    gi2-0-0.core01.lax01.atlas.cogentco.com (154.54.2.101)  74.545 ms
    gi3-0-0.core01.lax01.atlas.cogentco.com (154.54.1.33)  73.660 ms
14  po15-0.core01.lax02.atlas.cogentco.com (66.28.4.181)  74.667 ms
    te4-1.ccr01.san01.atlas.cogentco.com (154.54.7.86)  72.560 ms
    po15-0.core01.lax02.atlas.cogentco.com (66.28.4.181)  74.514 ms
15  gi7-2.hc01.lax02.atlas.cogentco.com (38.20.34.6)  74.460 ms  74.680 ms  74.912 ms
16  38.103.63.16 (38.103.63.16)  74.691 ms  75.255 ms
    te3-4.mpd01.lax01.atlas.cogentco.com (154.54.3.38)  74.799 ms

How fast is my connection?

While we can't measure the raw speed -- or bandwidth -- of your connection, we can measure the latency, or delay, of the connection. Latency can impact the speed of web browsing, voice conferencing, and other activities. We will send 10 pings to 38.103.63.16; this will take at least 10 seconds to complete.

PING 38.103.63.16 (38.103.63.16): 56 data bytes
64 bytes from 38.103.63.16: icmp_seq=0 ttl=54 time=75.188 ms
64 bytes from 38.103.63.16: icmp_seq=1 ttl=54 time=75.509 ms
64 bytes from 38.103.63.16: icmp_seq=2 ttl=54 time=75.641 ms
64 bytes from 38.103.63.16: icmp_seq=3 ttl=54 time=75.570 ms
64 bytes from 38.103.63.16: icmp_seq=4 ttl=54 time=74.852 ms
64 bytes from 38.103.63.16: icmp_seq=5 ttl=54 time=75.880 ms
64 bytes from 38.103.63.16: icmp_seq=6 ttl=54 time=75.048 ms
64 bytes from 38.103.63.16: icmp_seq=7 ttl=54 time=75.317 ms
64 bytes from 38.103.63.16: icmp_seq=8 ttl=54 time=74.342 ms
64 bytes from 38.103.63.16: icmp_seq=9 ttl=54 time=74.510 ms

--- 38.103.63.16 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 74.342/75.186/75.880/0.475 ms

(If the above results indicate 100% packet loss, it probably means that ping is blocked at your location.)

Configure Netdiag

You can modify the following options and re-run the test by selecting the Submit button.