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.107.179.236

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 236.179.107.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.42 (192.168.1.42)  0.402 ms  0.504 ms  0.334 ms
 3  0.xe-1-3-0.GW10.IAD8.ALTER.NET (152.179.50.137)  6.579 ms  6.723 ms  6.703 ms
 4  0.xe-7-1-3.XL3.IAD8.ALTER.NET (152.63.33.198)  6.705 ms  6.756 ms  6.688 ms
 5  0.ae3.BR2.IAD8.ALTER.NET (152.63.41.229)  6.595 ms
    0.ae3.BR1.IAD8.ALTER.NET (152.63.33.117)  6.608 ms
    0.ae3.BR2.IAD8.ALTER.NET (152.63.41.229)  6.602 ms
 6  te0-6-0-3.ccr21.iad02.atlas.cogentco.com (154.54.13.137)  6.938 ms  7.091 ms
    te0-6-0-0.ccr21.iad02.atlas.cogentco.com (154.54.12.45)  6.932 ms
 7  te0-2-0-4.ccr21.dca01.atlas.cogentco.com (154.54.1.77)  8.245 ms
    te0-3-0-5.ccr21.dca01.atlas.cogentco.com (154.54.2.49)  7.604 ms
    te0-1-0-5.ccr21.dca01.atlas.cogentco.com (154.54.26.129)  7.616 ms
 8  te0-3-0-7.ccr21.atl01.atlas.cogentco.com (154.54.42.194)  36.098 ms
    te0-3-0-2.ccr21.atl01.atlas.cogentco.com (154.54.42.190)  36.223 ms
    te0-2-0-6.ccr21.atl01.atlas.cogentco.com (154.54.2.45)  35.937 ms
 9  te0-1-0-2.ccr21.iah01.atlas.cogentco.com (154.54.2.82)  35.834 ms
    te0-0-0-6.ccr21.iah01.atlas.cogentco.com (154.54.29.2)  36.226 ms
    te0-0-0-1.ccr21.iah01.atlas.cogentco.com (154.54.24.18)  35.853 ms
10  te0-3-0-6.ccr21.lax01.atlas.cogentco.com (154.54.0.237)  71.325 ms
    te0-2-0-5.ccr21.lax01.atlas.cogentco.com (154.54.0.233)  71.147 ms
    te0-2-0-3.ccr21.lax01.atlas.cogentco.com (154.54.44.242)  71.320 ms
11  te4-4.ccr02.lax04.atlas.cogentco.com (154.54.1.10)  156.312 ms
    te3-8.ccr02.lax04.atlas.cogentco.com (154.54.24.70)  195.884 ms
    te4-4.ccr02.lax04.atlas.cogentco.com (154.54.1.10)  213.609 ms
12  vl3809.na41.b020097-1.lax04.atlas.cogentco.com (38.20.41.2)  71.514 ms  71.424 ms  71.541 ms
13  embark.demarc.cogentco.com (38.99.246.2)  71.494 ms  71.442 ms  71.385 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
31  * * *
32  * * *
33  * * *
34  * * *
35  * * *
36  * * *
37  * * *
38  * * *
39  * * *
40  * * *
41  * * *
42  * * *
43  * * *
44  * * *
45  * * *
46  * * *
47  * * *
48  * * *
49  * * *
50  * * *
51  * * *
52  * * *
53  * * *
54  * * *
55  * * *
56  * * *
57  * * *
58  * * *
59  * * *
60  * * *
61  * * *
62  * * *
63  * * *
64  * * *

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.107.179.236; this will take at least 10 seconds to complete.

PING 38.107.179.236 (38.107.179.236): 56 data bytes
64 bytes from 38.107.179.236: icmp_seq=0 ttl=56 time=71.734 ms
64 bytes from 38.107.179.236: icmp_seq=1 ttl=56 time=72.014 ms
64 bytes from 38.107.179.236: icmp_seq=2 ttl=56 time=71.842 ms
64 bytes from 38.107.179.236: icmp_seq=3 ttl=56 time=71.946 ms
64 bytes from 38.107.179.236: icmp_seq=4 ttl=56 time=71.832 ms
64 bytes from 38.107.179.236: icmp_seq=5 ttl=56 time=71.670 ms
64 bytes from 38.107.179.236: icmp_seq=6 ttl=56 time=71.836 ms
64 bytes from 38.107.179.236: icmp_seq=7 ttl=56 time=72.075 ms
64 bytes from 38.107.179.236: icmp_seq=8 ttl=56 time=71.740 ms
64 bytes from 38.107.179.236: icmp_seq=9 ttl=56 time=71.585 ms

--- 38.107.179.236 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 71.585/71.827/72.075/0.145 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.