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

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 56.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.41 (192.168.1.41)  0.523 ms  0.861 ms  0.848 ms
 3  63.65.185.1 (63.65.185.1)  13.963 ms  14.364 ms  13.964 ms
 4  0.so-1-0-2.XL4.IAD8.ALTER.NET (152.63.41.18)  13.877 ms  14.552 ms  13.843 ms
 5  0.ge-3-3-0.BR2.IAD8.ALTER.NET (152.63.40.229)  14.015 ms
    0.ge-7-0-0.BR2.IAD8.ALTER.NET (152.63.41.157)  13.734 ms
    0.ge-5-1-0.BR2.IAD8.ALTER.NET (152.63.41.233)  14.595 ms
 6  te3-6.mpd01.iad01.atlas.cogentco.com (154.54.13.137)  16.639 ms  16.488 ms  16.836 ms
 7  * * te1-2.ccr02.iad01.atlas.cogentco.com (154.54.26.93)  16.654 ms
 8  * * *
 9  te2-2.mpd01.lax01.atlas.cogentco.com (154.54.5.102)  81.191 ms  81.195 ms
    te3-1.ccr01.iah01.atlas.cogentco.com (154.54.2.82)  51.910 ms
10  te3-2.ccr01.lax01.atlas.cogentco.com (154.54.0.225)  80.675 ms
    te2-1.ccr02.lax01.atlas.cogentco.com (154.54.5.194)  81.577 ms  81.344 ms
11  te7-1.ccr02.lax01.atlas.cogentco.com (154.54.0.54)  79.838 ms
    te9-5.ccr01.lax01.atlas.cogentco.com (154.54.2.117)  81.523 ms
    te4-4.ccr01.lax02.atlas.cogentco.com (154.54.27.130)  81.772 ms
12  gi7-2.hc01.lax02.atlas.cogentco.com (38.20.34.6)  80.634 ms
    te4-4.ccr01.lax02.atlas.cogentco.com (154.54.27.130)  81.671 ms
    te4-2.ccr01.lax02.atlas.cogentco.com (154.54.27.126)  81.234 ms
13  * * gi5-2.hc01.lax02.atlas.cogentco.com (38.112.36.250)  80.731 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.103.63.56; this will take at least 10 seconds to complete.

PING 38.103.63.56 (38.103.63.56): 56 data bytes
64 bytes from 38.103.63.56: icmp_seq=0 ttl=50 time=81.770 ms
64 bytes from 38.103.63.56: icmp_seq=1 ttl=50 time=82.395 ms
64 bytes from 38.103.63.56: icmp_seq=2 ttl=50 time=81.548 ms
64 bytes from 38.103.63.56: icmp_seq=3 ttl=50 time=81.581 ms
64 bytes from 38.103.63.56: icmp_seq=4 ttl=50 time=81.852 ms
64 bytes from 38.103.63.56: icmp_seq=5 ttl=50 time=81.878 ms
64 bytes from 38.103.63.56: icmp_seq=6 ttl=50 time=81.905 ms
64 bytes from 38.103.63.56: icmp_seq=7 ttl=50 time=82.058 ms
64 bytes from 38.103.63.56: icmp_seq=8 ttl=50 time=81.213 ms
64 bytes from 38.103.63.56: icmp_seq=9 ttl=50 time=82.238 ms

--- 38.103.63.56 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 81.213/81.844/82.395/0.327 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.