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

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 109.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)  0.822 ms  1.013 ms  1.082 ms
 3  GigabitEthernet0-1-0-2.GW1.IAD8.ALTER.NET (152.179.50.5)  14.791 ms  13.994 ms  21.218 ms
 4  0.ge-3-0-0.XL4.IAD8.ALTER.NET (152.63.35.150)  14.364 ms  17.603 ms  14.811 ms
 5  0.xe-11-1-0.BR1.IAD8.ALTER.NET (152.63.41.161)  15.094 ms
    0.xe-10-1-0.BR1.IAD8.ALTER.NET (152.63.41.157)  14.498 ms
    0.xe-9-1-0.BR1.IAD8.ALTER.NET (152.63.40.229)  14.384 ms
 6  te4-2.ccr01.iad01.atlas.cogentco.com (154.54.10.225)  12.792 ms
    te3-6.mpd01.iad01.atlas.cogentco.com (154.54.13.137)  12.353 ms
    te4-2.ccr01.iad01.atlas.cogentco.com (154.54.10.225)  12.302 ms
 7  te0-2-0-4.ccr21.dca01.atlas.cogentco.com (154.54.1.77)  13.369 ms
    te1-2.ccr02.iad01.atlas.cogentco.com (154.54.26.93)  11.715 ms
    te0-2-0-4.ccr21.dca01.atlas.cogentco.com (154.54.1.77)  13.542 ms
 8  te4-2.mpd01.atl01.atlas.cogentco.com (154.54.28.225)  40.324 ms
    te3-8.mpd01.atl01.atlas.cogentco.com (154.54.28.18)  43.319 ms
    te3-8.ccr01.atl01.atlas.cogentco.com (154.54.24.10)  43.281 ms
 9  te7-3.ccr02.atl01.atlas.cogentco.com (154.54.28.57)  40.223 ms
    te3-1.ccr01.iah01.atlas.cogentco.com (154.54.2.82)  40.529 ms
    te9-2.ccr01.iah01.atlas.cogentco.com (154.54.25.118)  40.589 ms
10  te2-2.mpd01.lax01.atlas.cogentco.com (154.54.5.102)  145.268 ms
    te9-1.ccr01.lax01.atlas.cogentco.com (154.54.0.233)  72.328 ms
    te3-1.ccr01.iah01.atlas.cogentco.com (154.54.2.82)  41.518 ms
11  te9-2.ccr02.lax01.atlas.cogentco.com (154.54.3.186)  72.426 ms
    te3-2.ccr01.lax04.atlas.cogentco.com (154.54.24.62)  73.265 ms
    te9-2.ccr02.lax01.atlas.cogentco.com (154.54.3.186)  72.518 ms
12  vl3509.na31.b020097-1.lax04.atlas.cogentco.com (38.20.40.250)  74.125 ms
    te3-2.ccr01.lax04.atlas.cogentco.com (154.54.24.62)  72.394 ms
    vl3509.na31.b020097-1.lax04.atlas.cogentco.com (38.20.40.250)  74.119 ms
13  vl3509.na31.b020097-1.lax04.atlas.cogentco.com (38.20.40.250)  73.523 ms *  76.104 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.109; this will take at least 10 seconds to complete.

PING 38.107.191.109 (38.107.191.109): 56 data bytes
64 bytes from 38.107.191.109: icmp_seq=0 ttl=51 time=72.943 ms
64 bytes from 38.107.191.109: icmp_seq=1 ttl=51 time=73.174 ms
64 bytes from 38.107.191.109: icmp_seq=2 ttl=51 time=72.558 ms
64 bytes from 38.107.191.109: icmp_seq=3 ttl=51 time=73.221 ms
64 bytes from 38.107.191.109: icmp_seq=4 ttl=51 time=73.560 ms
64 bytes from 38.107.191.109: icmp_seq=5 ttl=51 time=72.687 ms
64 bytes from 38.107.191.109: icmp_seq=6 ttl=51 time=72.821 ms
64 bytes from 38.107.191.109: icmp_seq=7 ttl=51 time=72.916 ms
64 bytes from 38.107.191.109: icmp_seq=8 ttl=51 time=73.072 ms
64 bytes from 38.107.191.109: icmp_seq=9 ttl=51 time=73.078 ms

--- 38.107.191.109 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 72.558/73.003/73.560/0.272 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.