PilotEdge Forums

31.170.162.83 - My pings all time out.

Gavin, and you can't use the web site, is that right? Same IP here, web site is working well for me.

Yup, can't get to the web site. I can get to www.web44.net though.

Here's my TraceRoute:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tracert findflight.web44.net

Tracing route to findflight.web44.net [31.170.162.83] over a maximum of 30 hops:

1 1 ms 3 ms <1 ms home [192.168.1.254]
2 23 ms 22 ms 23 ms 99-1-40-2.lightspeed.mmphtn.sbcglobal.net [99.1.40.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 23 ms 23 ms 22 ms 70.159.236.146
7 29 ms 28 ms 28 ms 12.81.52.62
8 32 ms 31 ms 32 ms 12.81.105.108
9 29 ms 30 ms 28 ms 12.81.32.109
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.

Not sure if it'll help, but here's my route to web44.net:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tracert web44.net

Tracing route to web44.net [208.43.151.204] over a maximum of 30 hops:

1 1 ms <1 ms 2 ms home [192.168.1.254]
2 961 ms 1141 ms 1174 ms 99-1-40-2.lightspeed.mmphtn.sbcglobal.net [99.1.40.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 22 ms 22 ms 23 ms 70.159.236.142
7 29 ms 29 ms 29 ms 12.81.52.20
8 30 ms 30 ms 31 ms 12.81.32.130
9 29 ms 30 ms 28 ms 12.81.32.111
10 29 ms 29 ms 33 ms 74.175.192.134
11 39 ms 40 ms 40 ms cr1.nsvtn.ip.att.net [12.122.148.14]
12 39 ms 39 ms 40 ms cr2.attga.ip.att.net [12.122.28.105]
13 37 ms 36 ms 52 ms attga02jt.ip.att.net [12.123.22.153]
14 37 ms 36 ms 37 ms 192.205.33.42
15 38 ms 36 ms 39 ms softlayer-ic-139991-atl-bb1.c.telia.net [213.248.102.206]
16 37 ms 36 ms 37 ms ae7.bbr01.tl01.atl01.networklayer.com [173.192.18.172]
17 60 ms 72 ms 56 ms ae13.bbr02.eq01.dal03.networklayer.com [173.192.18.134]
18 67 ms 67 ms 74 ms ae1.bbr01.cs01.den01.networklayer.com [173.192.18.139]
19 97 ms 97 ms 96 ms ae0.bbr01.wb01.sea02.networklayer.com [173.192.18.144]
20 97 ms 97 ms 96 ms ae0.dar01.sr01.sea01.networklayer.com [173.192.18.199]
21 96 ms 95 ms 96 ms po1.fcr01.sr01.sea01.networklayer.com [67.228.118.134]
22 100 ms 96 ms 96 ms hosting24.com [208.43.151.204]
Trace complete.

It's not an DNS issue, that much is clear. Something is blocking you from reaching that IP. That's pretty rare.

Interesting... I have access to several VPNs around the country. Phoenix, Los Angeles and Miami all led to no connection.

I did get the site to come up when I connected to the Newark, NJ VPN.

It appears that some ISP's are blocking content from some or all of the IP's from http://www.000webhost.com/. Since it's free hosting, there is all kinds of stuff hosted there. When an ISP has a problem with one of the sites, they block the IP address but that IP is not unique to a single site......it is shared by the all the sites on that server. I'm guessing that might be the case here.

Free web hosting.....you get what you pay for.

Still looking for alternatives...

Very nice work Ken!

Receiving a connection timeout when I attempt to ping the address through cmd in windows, KS. MidCo Internet user here.

Hi Ken, very neat application, I will be using it, I also see the link to file PE flight plan. I hope others can figure out the problems with opening it, works fine here. Thank you for sharing. Cheers, AJ