By Support on
7/24/2008 9:47 AM
We are finishing the install with another high bandwidth circuit tonight @ 8pm PST. Although we don't anticipate any long network down time, we may be doing some failover testing's to make sure our BGP configurations are doing what we want/expect, which may make us appear to be down for 30 second intervals. Being that we are multi-homed with several different providers, this additional bandwidth will make your response times even better. We will be peering direct with Level3 on this circuit.
|
By Support on
7/17/2008 8:07 AM
We have confirmed a report from one Charter customer in the California area is having problems connecting to our network. We are aware of the issue, and our service providers are working diligently to resolve this. We are sorry for any inconvenience this may have caused. Although we are not responsible for this, we want you to know that we are applying as much pressure as we can to get this problem resolved. If you are experiencing the same issue, please let us know immediately. 775-331-3319.
|
By Support on
6/4/2008 10:29 AM
Well, for the first time in our history we got to use our generators. We have been very lucky for 10 years, but it was bound to happen. This morning (6/4/08), Reno Nevada was hit by a major power outage. Our systems flipped over to our generator and worked like a charm, but our network room for some reason did not. We were able to resolve that problem by pulling power from our DataCenter to our Network Room. During that time, our network appeared offline although the servers were all up and running. We apologize if this outage caused you any troubles. We are working on a plan to prevent this from happening again (well, our part - we cant help the power company). As of this posting, power has been restored, and we will be flipping back to standard power in the next few minutes.
|
By Support on
5/23/2008 8:23 AM
We are doing some major upgrades on our network this next week. We have one of our two new providers installed and ready to go. We just have to configure our routers to start using them. One of our new connection is a connection that can burst to gig speeds. Yes.. that's right.. 1000 Megabits per second. Our other provider should be installed at the end of next week. The network switchover will be transparent to you with the exception of some serious fast speeds. We may have one of our networks online by the weekend, or early next week.
|
By Support on
2/27/2008 10:13 PM
After hours of researching and trouble shooting with our providers, Verizon posts up on their network status page that they are having problems like crazy. http://wapp.verizon.net/systemstatus/status.asp?status_type=DSL We are happy to know its not us, but sad that this is happening because customers cant get to our networks. They must be working on it because everything just went online as I was typing this blog post. 
|
By Support on
2/27/2008 5:39 PM
We have been researching an issue where customers are having a hard time getting to AMHosting.com and their websites. Our network admins have researched this, and talked to our providers to determine that its not an issue of AMHosting, but a major backbone issue from an Los Angeles Router to a router in Albyny New York. This is a major pipe that is experiencing some major network problems outside the control of AMHosting. Our providers are working on a fix, which might include selecting a different path for routing to not use the Los Angeles peering point. On the screen shot above, you can see that there is no packet loss from our upstream providers, or their upstream provider. The packet loss happens at 130.91.19.110. If you are having this problem, you really cant even read this blog post until Verizon fixes this issue on their network.. We will post up a voice notice on our phone system. We apologize for the inconvenience.
|
By Support on
2/5/2008 9:10 AM
We just had a small network glitch. One of our DS3s went offline for about 11 minutes. You may have saw some latency changes, but our backup DS3s did their job. Everything is back up and running fine now.
Read More »
|