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

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 92.191.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.41 (192.168.1.41)  1.331 ms  2.154 ms  1.835 ms
 3  GigabitEthernet0-1-0-2.GW1.IAD8.ALTER.NET (152.179.50.5)  14.907 ms  14.676 ms  14.811 ms
 4  0.xe-3-1-2.XL3.IAD8.ALTER.NET (152.63.35.146)  14.696 ms  14.540 ms  15.082 ms
 5  0.ae3.BR1.IAD8.ALTER.NET (152.63.33.117)  14.726 ms  14.564 ms  51.175 ms
 6  te0-7-0-1.ccr21.iad02.atlas.cogentco.com (154.54.10.225)  12.781 ms  12.771 ms  12.956 ms
 7  te0-2-0-4.ccr21.dca01.atlas.cogentco.com (154.54.1.77)  13.472 ms  17.854 ms
    te0-3-0-5.ccr21.dca01.atlas.cogentco.com (154.54.2.49)  13.555 ms
 8  te3-1.ccr01.atl01.atlas.cogentco.com (154.54.28.202)  41.108 ms
    te7-2.ccr01.atl01.atlas.cogentco.com (154.54.28.214)  43.427 ms  43.497 ms
 9  te4-2.ccr01.atl01.atlas.cogentco.com (154.54.28.237)  40.739 ms  40.597 ms
    te0-3-0-2.ccr21.iah01.atlas.cogentco.com (154.54.25.118)  41.685 ms
10  te3-1.ccr01.lax01.atlas.cogentco.com (154.54.0.221)  73.189 ms
    te0-1-0-2.ccr21.iah01.atlas.cogentco.com (154.54.2.82)  42.248 ms
    te0-2-0-1.ccr21.iah01.atlas.cogentco.com (154.54.29.6)  41.409 ms
11  te4-2.ccr01.lax04.atlas.cogentco.com (154.54.24.70)  73.219 ms  73.263 ms
    te3-2.ccr01.lax04.atlas.cogentco.com (154.54.24.62)  73.153 ms
12  vl3509.na41.b020097-1.lax04.atlas.cogentco.com (38.20.40.250)  73.433 ms
    vl3809.na41.b020097-1.lax04.atlas.cogentco.com (38.20.41.2)  73.362 ms
    vl3509.na41.b020097-1.lax04.atlas.cogentco.com (38.20.40.250)  73.268 ms
13  ahtky-ins.demark.cogentco.com (38.104.82.34)  72.934 ms  73.387 ms  72.916 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.191.92; this will take at least 10 seconds to complete.

PING 38.107.191.92 (38.107.191.92): 56 data bytes
64 bytes from 38.107.191.92: icmp_seq=0 ttl=50 time=72.903 ms
64 bytes from 38.107.191.92: icmp_seq=1 ttl=50 time=73.244 ms
64 bytes from 38.107.191.92: icmp_seq=2 ttl=50 time=73.142 ms
64 bytes from 38.107.191.92: icmp_seq=3 ttl=50 time=73.969 ms
64 bytes from 38.107.191.92: icmp_seq=4 ttl=50 time=73.271 ms
64 bytes from 38.107.191.92: icmp_seq=5 ttl=50 time=73.082 ms
64 bytes from 38.107.191.92: icmp_seq=6 ttl=50 time=72.648 ms
64 bytes from 38.107.191.92: icmp_seq=7 ttl=50 time=72.800 ms
64 bytes from 38.107.191.92: icmp_seq=8 ttl=50 time=73.198 ms
64 bytes from 38.107.191.92: icmp_seq=9 ttl=50 time=73.927 ms

--- 38.107.191.92 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 72.648/73.218/73.969/0.412 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.