my site is being weird

[Jake_82]

my site is acting strangely... when I go to "http://www.oasisx.com", the page won't load at all (or any other pages/files on the domain), but I can still access my ftp and email. however, for some unknown reason, the site sometimes loads when I go to "http://oasisx.com" and write the domain that way...

I think this may have begun a few hours ago when I got an error related to a PHP file... any suggestions?

thanks!

[HalfaBee]

Which server are you on?

[(jj)]

Have you tried clearing your browser cache files?

I can get to http://www.oasisx.com/ just fine:
"Latest news=18 July: Production has begun"

[HalfaBee]

G'Day JJ,

I can't even ping the site.

It must be a downunder problem. :(

I asked about the server name because I get an unreachable error while trying to ping.

[(jj)]

G'Day HalfaBee,

Well this is odd. I just checked and I can go anywhere on the site "oasisx.com" but when I ran a tracert it stopped at Internap and timed out beyond there.

Yet I can click on any menu option of oasisx.com and the pages will load. And I'm sure that it's not from MY cache *s*.

<edit>
But a ping will answer back with 4 good return packets :confused:
</edit>

[HalfaBee]

This is what I get from Pingplotter
Hope this is readable. :(

Target Name: oasisx.com
IP: 63.251.213.10
Date/Time: 24/11/2003 9:56:30

1 * * * * * * * [-]
2 152 ms 121 ms 141 ms 113 ms 125 ms 114 ms 110 ms hsrp.vlan14-kent-syd.comindico.com.au [203.194.60.254]
3 332 ms 303 ms 296 ms 306 ms 302 ms 284 ms 319 ms ge6-1.cor01-kent-syd.comindico.com.au [203.194.28.233]
4 314 ms 300 ms 299 ms 307 ms 308 ms 288 ms 311 ms pos3-1.155.cor01-alex-scn.comindico.net.au [203.194.0.166]
5 321 ms 326 ms 329 ms 302 ms 294 ms 305 ms 318 ms pos0-0.155.cor01-maew-sjc.comindico.net [203.194.0.73]
6 307 ms 304 ms 314 ms 306 ms 308 ms 315 ms 306 ms ge0-0.1000.bdr02-maew-sjc.comindico.net [203.194.0.198]
7 1588 ms 1515 ms 1541 ms 1533 ms 1535 ms 1627 ms 1610 ms unknown.Level3.net [166.90.143.93]
8 1530 ms 1491 ms 1528 ms 1513 ms 1523 ms 1571 ms 1589 ms unknown.Level3.net [64.159.2.129]
9 1574 ms 1524 ms 1535 ms 1549 ms 1558 ms 1595 ms 1585 ms so-1-0-0.bbr1.LosAngeles1.Level3.net [209.247.9.113]
10 1564 ms 1510 ms 1541 ms 1546 ms 1563 ms 1599 ms 1566 ms so-8-0.core2.LosAngeles1.Level3.net [209.247.10.198]
11 1540 ms 1520 ms 1561 ms 1548 ms 1560 ms 1582 ms 1553 ms ge-6-0.ipcolo2.LosAngeles1.Level3.net [209.244.10.46]
12 1557 ms * 1554 ms 1541 ms 1539 ms 1583 ms 1544 ms unknown.Level3.net [63.208.234.134]
13 1514 ms * 1569 ms 1549 ms 1535 ms 1620 ms 1537 ms border1.ge4-1-bbnet2.ext1a.lax.pnap.net [216.52.255.95]
14 * * * * * * * [-]
15 * * * * * * * [-]
16 * * * * * * * [-]

[(jj)]

That's about the same as what I got with HyperTrace. Yet a DOS ping will return as ok and I'm browsing the site at the same time that the trace came back as unreachable. :confused:

Guess Jake_82 was right when he said it was being "weird"

[HalfaBee]

Time to sit back and crack open a coldie. :D

No use wasting time on something you can't fix.

[HalfaBee]

Just for a laugh I pinged NS3.powweb.com and got ns2.powweb.com
When I pinged ns2.powweb.com, I got ns3.powweb.com.

Ooopps.

[Jake_82]

well whatever happened, it seems to have gone back in to working order... I guess it was just a momentary lapse into the mysterious zone between sunday night and monday morning when everything is not what it seems ;)