| Posted by Xandrios, 12-03-2007, 02:24 PM | |
Is olm.net down again? My servers with them seem to be all unresponsive at once...
|
| Posted by Pomond, 12-03-2007, 03:10 PM | |
Hiya:
From where I'm sitting, OLM.net has been offline for about the past hour. (It's currently a little after 1 p.m. Central Time, U.S.).
My VPS sites and other client sites hosted at OLM are all offline; even the main www.olm.net site seems to be down. Is anyone else seeing this or affected by it?
|
| Posted by Xandrios, 12-03-2007, 03:12 PM | |
Unfortunately yes: <>
Are you able to get through at their phone support line?
Last edited by bear; 12-03-2007 at 03:29 PM.
|
| Posted by Xandrios, 12-03-2007, 03:18 PM | |
One of my servers just came back online. Others still down though...
|
| Posted by Fizzadar, 12-03-2007, 03:20 PM | |
It's down here too...
|
| Posted by Xandrios, 12-03-2007, 03:26 PM | |
And mine went back offline again as well
|
| Posted by OLMNET, 12-03-2007, 03:31 PM | |
I can confirm there is a portion of the network down currently. I will get details asap and report back.
-Chris@OLM
|
| Posted by OLMNET, 12-03-2007, 03:36 PM | |
No sooner did I hit submit than I got word everything is back to normal. I will report back on what happened.
-Chris@OLM
|
| Posted by Xandrios, 12-03-2007, 03:41 PM | |
Thanks Chris
When will the redundant status website be available that you were talking about here?
|
| Posted by Pomond, 12-03-2007, 03:44 PM | |
Looks like I and all of my sites are back online as well; it's now about 1:45 p.m. Central Time, a little less than a 2 hour outage.
|
| Posted by pinoyup, 12-03-2007, 03:45 PM | |
Hmm, strange, olm.net and serveraday.com is offline as well as their dns ns1.fastdns.net and ns2.fastdns.net but my server from olm's serveraday.com is online. My IP address is from this range:
69.94.0.0 - 69.94.127.255
|
| Posted by OLMNET, 12-03-2007, 04:07 PM | |
We had an unexpected corruption of the VLAN information in a core Cisco switch, which caused an interruption for a segment of our network. After troubleshooting and isolating the issue, our Administrators decided the best option was to replace the switch, and reload the configuration accordingly. Since this problem related to actual corruption in the VLAN database, the redundancy which is built into our network was unable to take effect.
-Chris@OLM
|
|
 Add to Favourites
 Print this Article
|
