The server will be down for approximately 30 minutes beginning at 9PM EST for security updates and re-imaging. Call 800.330.1951 if you would like to reschedule.
-
Recent Posts
Recent Comments
Archives
Categories
Meta
The server will be down for approximately 30 minutes beginning at 9PM EST for security updates and re-imaging. Call 800.330.1951 if you would like to reschedule.
https://technet.microsoft.com/en-us/library/security/ms17-010.aspx
Currently, a very active security leak is being exploited on Windows
systems. Systems with the latest security updates from Microsoft should not
be affected.
As the server administrator, you are responsible for the security of your
server and for regularly installing security updates. Please check that
your server has all the latest security updates installed. If this is not
the case, please install the updates immediately.
You can find more information on the security leak at the link below:
https://technet.microsoft.com/
4a.m. EST, to apply updates and add an additional 1/2 terrabyte of storage to the server. The Amsoft Cloud will be down for under 7 minutes. We apologize for any inconvenience.
Cloud1.Amsoftcloud.com will be down tonight beginning at 7:30 EST., and is scheduled to come back online before 7:35EST. for a routine planned re-imaging of the operating system.
The recent outage was a doozy, lasting over 12 hours. This entry will detail what happened, and what steps we are taking to mitigate the effect on our cloud beta testers. First, I received this email an hour before the servers went down:
Your security is important to use and we are therefore running an urgent
security update on our 1&1 DCS Servers this week. This is update is
necessary because a new vulnerability was discovered in the Citrix and Xen
Hypervisor, affecting all DCS servers.We will begin resolving this issue shortly.
What this means for you: During the update, your server will be unavailable
between 10 minutes and 2 hours. Data loss is highly unlikely. We apologize
that we cannot give you a definite time frame for the maintenance of your
system.Please also note: This vulnerability is not related to the current Shell
Shock vulnerability.For more information about the vulnerability, refer to number XSA-108 on
the following page:
http://xenbits.xen.org/xsa/We apologize for any inconvenience this may cause you.
In short, the vulnerability was leaked to security companies before the public, and the security people at the server company and their upstream data providers pulled the plug in order to prevent data theft of epic proportion.
What we learned, and what we’re changing: