Results 1 to 5 of 5
Thread: Lunarpages still active ??
-
03-07-2004, 02:04 PM #1Newbie
- Join Date
- Dec 2003
- Location
- United States
- Posts
- 21
Lunarpages still active ??
I haven't been able to log onto any of my websites on two different Lunarpages servers at all today. Also, I can't bring up their official forums and not even their home page.
I can access every other website I want to, just nothing related to Lunarpages. So I'm wondering if the company went out of business, or if it's just some technical problem that's got their entire network offline for so many hours.
Any info would be appreciated.
-
03-07-2004, 02:08 PM #2Web Hosting Master
- Join Date
- Jan 2003
- Location
- Lake Arrowhead, CA
- Posts
- 789
They all work fine from here.
http://www.srohosting.com
Stability, redundancy and peace of mind
-
03-07-2004, 02:09 PM #3Web Hosting Master
- Join Date
- Oct 2001
- Location
- Ohio
- Posts
- 8,535
It loooks like it's a problem with your ISP as I am able to access their website and forums fine. Maybe if you did a tracert we could find out where the problem lies?
-
03-07-2004, 02:11 PM #4Junior Guru Wannabe
- Join Date
- Jan 2004
- Location
- SoCal
- Posts
- 63
My LunarPages sites work fine as usual and the forums work as well.
-
03-07-2004, 02:42 PM #5Newbie
- Join Date
- Dec 2003
- Location
- United States
- Posts
- 21
Thanks for the feedback !!
I ran a trace and it appears that the connection is getting hung up in some kind of loop at wcg.net (Williams Communications Group)...
64.200.227.141 - 151ms - tulsok6wcx3-ser5-0.wcg.net
64.200.240.81 - 138ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 151ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 151ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 137ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 178ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 165ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 165ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 151ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 164ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 165ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 165ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 165ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 179ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 165ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 179ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 178ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 193ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 192ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 192ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 179ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 192ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 206ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 206ms - dllstx1wcx3-oc48.wcg.net
64.200.240.82 - 206ms - tulsok6wcx3-oc48.wcg.net
64.200.240.81 - 205ms - dllstx1wcx3-oc48.wcg.net
Now to figure out a way to route around that lame duck wcg.net network.