File Archive Not Working


White Demon

Sandy Wich's Boy
Joined
Sep 16, 2004
Messages
842
Location
South Australia
Website
Visit site
I've been trying to get into the GP2X file archive since last night (Aussie time, about 12 hours ago) and every time I try I either get 'page timed out/server taking too long to respond' or the top of the page loads (v-e-r-y slowly) and nothing else. I can't get into it at all.

These forums are unaffected, it's just the archive that's not working. What's going on?
 
White Demon posted on Dec 27 2006 at 07:52 PM said:
I've been trying to get into the GP2X file archive since last night (Aussie time, about 12 hours ago) and every time I try I either get 'page timed out/server taking too long to respond' or the top of the page loads (v-e-r-y slowly) and nothing else. I can't get into it at all.

These forums are unaffected, it's just the archive that's not working. What's going on?


Working fine now. Try pinging the website. Compare that ping to a ping on Google or Yahoo.
 
Last edited by a moderator:
It's still not working good. Sometimes I get a page up (VERY slowly), but can't get a download at all.

I pinged both the archive and google (for comparison) TWICE, here's the ping results:

ping www.gp2x.de

Pinging gp2x.de [80.237.211.118] with 32 bytes of data:

Reply from 80.237.211.118: bytes=32 time=606ms TTL=50
Request timed out.
Reply from 80.237.211.118: bytes=32 time=620ms TTL=50
Request timed out.

Ping statistics for 80.237.211.118:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 606ms, Maximum = 620ms, Average = 613ms

ping www.google.com

Pinging www.l.google.com [66.102.7.99] with 32 bytes of data:

Reply from 66.102.7.99: bytes=32 time=202ms TTL=244
Reply from 66.102.7.99: bytes=32 time=202ms TTL=244
Reply from 66.102.7.99: bytes=32 time=201ms TTL=244
Reply from 66.102.7.99: bytes=32 time=201ms TTL=244

Ping statistics for 66.102.7.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 202ms, Average = 201ms

ping www.gp2x.de

Pinging gp2x.de [80.237.211.118] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.237.211.118:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping www.google.com

Pinging www.l.google.com [66.102.7.99] with 32 bytes of data:

Reply from 66.102.7.99: bytes=32 time=201ms TTL=244
Reply from 66.102.7.99: bytes=32 time=208ms TTL=244
Reply from 66.102.7.99: bytes=32 time=202ms TTL=244
Reply from 66.102.7.99: bytes=32 time=203ms TTL=244

Ping statistics for 66.102.7.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 208ms, Average = 203ms

So something must be wrong with the site.
 
Fine here also (UK), probably some fish nibbling on the Auz underwater cables :p

[edit]

Doing a tracert www.gp2x.de should give you more ideas of where the problem is, heres mine with my ip/initial hops removed :p

4 8 ms 10 ms 8 ms 195.182.175.73
5 22 ms 8 ms 8 ms 213.105.175.1
6 37 ms 12 ms 17 ms 62.253.187.178
7 10 ms 23 ms 9 ms 213.105.175.141
8 15 ms 14 ms 16 ms 62.253.185.238
9 16 ms 36 ms 24 ms 62.253.184.6
10 17 ms 15 ms 15 ms 212.250.14.42
11 16 ms 42 ms 15 ms 62.72.137.10
12 159 ms 68 ms 43 ms 62.72.139.18
13 75 ms 42 ms 44 ms 80.237.211.118

Trace complete.
 
All of the response times for the pings White Demon sent out are pretty bad.
Maybe its something to do with that underwater earthquake from tuesday that's taken out almost all of the internet connections in Asia? (Either the auzy ISP's routing the internet through asia, or the asians now taking all of the auzys bandwidth up now that they are getting connected again through different cables).

If it's not that, maybe it's a sign from the gods that you need to have more barbys and drink more larger?
 
Seems to be fine now. Pings still occasionally miss, but I can access the archive with little problems, just a little slower than what I'm used to for now.

Maybe it did/does have something to do with the Asian internet connections, seems rather strange though that only the GP2X archive & parts of psphacks.com would be affected while anything else I tried to access worked without any problems.
 
Back
Top