Archive for 1st March 2010
Cloud Sites | SAT | MySQL5-20.wc1 & MySQL50-23.wc1 | March 2, 3:00 – 6:00am CST
On March 2nd from 03:00am – 06:00am CST, The Rackspace Cloud system administrators will be
performing priority maintenance on two of our MySQL database clusters in
our SAT data center.
During the
maintenance window some SQL queries utilizing these clusters will be in a
read locked state (INSERT, UPDATE, DELETE, ALTER queries will be
ignored) for the duration of the maintenance. There may be a period of
up to 10 minutes in which databases will be unavailable.
We
expect this maintenance to last no longer than the time listed. We
apologize for the inconvenience, but we need to complete this work in a
timely manner. Please note that no other technologies will be effected
by this maintenance.
UPDATE: Cloud Engineers have rolled back maintenance changes and the servers are back online.
Investigation Complete – Issue Resolved
Cloud Sites | Control Panel Maintenance | March 2nd 10:00 PM – 11:00 PM CST | Completed
The Rackspace Cloud’s system engineering team will be performing control
panel maintenance on Tuesday, March 2nd, 2010 from 10:00 PM to
11:00 PM CST. During this maintenance the control panel will be temporarily offline. We expect this maintenance
to be completed within this time window and as always work to keep
maintenance down to a minimum.Â
UPDATE:Â As of 10:41 pm CST, Our Rackspace Cloud Engineers have completed the maintenance and everything should be back online.
If you have any issues, please do not hesitate to contact a
member of our support team via live-chat or at the following
telephone numbers: 24-hour toll free 1.877.934.0407 and INTL
+1.210.581.0407.
Issue at 10:08 AM CST (16:08 GMT)
Highrise search was down for about 15 minutes this morning. We’re sorry for the trouble.
RESOLVED – Network issues affecting some Linodes in Newark
8:42am (EST): Network issues in Newark should be resolved at this time.
8:24am (EST): We are currently investigating network issues in the Newark, NJ facility. There is no reason to issue reboots and we will post an update shortly.



