January 31, 2012, 3:55 pm
On Tuesday, January 31st 2012 from 10:00 PM to 11:00 PM CST, Rackspace Cloud Sites will undergo a critical maintenance in our DFW-WC2 datacenter. Customers using Cloud Sites may experience brief service interruptions or site degradation until completion.
We apologize for the inconvenience. If you have any questions, please contact a member of our support team by visiting us in live-chat or by calling 1.877.934.0407 or INTL +1.210.581.0407.
January 31, 2012, 3:21 pm
2012-01-31T17:07:33Z
2012-01-31T17:07:33Z
Online
Investigation Complete – This alert is hidden from users because the title is blank.
January 31, 2012, 3:21 pm
2012-01-31T17:21:02Z
2012-01-31T17:21:02Z
Online
Investigation Complete – This alert is hidden from users because the title is blank.
January 31, 2012, 3:14 pm
On Tuesday, January 31st, 2012 from 10:00 PM – 12:00 AM CST, The Rackspace Cloud will conduct an Emergency Maintenance on our Cloud Servers infrastructure. We do not anticipate any impact to services including Cloud Servers, the Cloud Servers Control Panel and the Cloud Servers API.
Update: Maintenance is in progress.
If you have any questions, please contact a member of our support team by visiting us in live-chat or by calling 1.877.934.0407 or INTL +1.210.581.0407.
January 31, 2012, 1:05 pm
At approximately 12:50 PM CST, Rackspace Cloud Engineers identified an issue with our Control Panel provisioning new sites. New sites are currently seeing errors in the Control Panel. Our Engineers are diligently working on the issue.
Update: As of about 1:20 PM CT, Cloud Engineers have resolved the issue and sites are creating properly.
Thank you for your patience during this matter. If you have any further questions, please contact a member of our support team by visiting us in live-chat or by calling 1.877.934.0407 or INTL+1.210.581.0407
January 31, 2012, 11:24 am
January 31, 05:23 PM GMT
ATL-B SAN4 is currently inaccessible. DC techs are investigating the issue
05:54 PM GMT The issue is still being checked
06:04 PM GMT SAN went down due to disk failure. It is now back online. All affected VMs are queued for startup
06:13 PM GMT All VM’s are back online. If you still experience any issues feel free to contact supp...@vps.net
January 31, 2012, 11:22 am
At approximately 10:50 AM CT, the Rackspace Cloud engineers identified an issue on PHP 5-21 in our ORD data center. Currently, the cluster is running in a degraded state. Our engineers are diligently working on resolving the issue.
UPDATE: As of 11:40 AM CT, Rackspace Engineers resolved the issue. Services are back to online status.
We really appreciate your patience and understanding of this matter. If you have any further questions, please contact a member of our support team by visiting us in live-chat or by calling 1.877.934.0407 or INTL +1.210.581.0407.
January 31, 2012, 11:16 am
As of about 10:45 AM CT, the Rackspace Cloud engineers identified an issue on MySQL 50-91 in our DFW1 data center. At this time, connections to this database server are intermittently affected. Our engineers are diligently working on resolving the issue.
Update: At about 11:40 AM CT, Cloud Administrators have looked into the issues on mysql50-91 and currently monitoring its activity.
Update: At about 12:40 PM CT, the MySQL 50-91 cluster began to experience degradation again, and our Engineers are currently investigating this issue. Thanks for your patience.
UPDATE: At about 2:15 PM CT, the Engineers made configuration changes to mitigate the effects of this intermittent issue. At this time, the issue has been resolved, and we will continue to monitor this cluster.
Thank you for your patience and understanding of this matter. If you have any further questions, please contact a member of our support team by visiting us in live-chat or by calling 1.877.934.0407 or INTL +1.210.581.0407.
January 31, 2012, 5:30 am
We continue to see error rates at normal levels. At this time we believe this incident was caused by a simultaneous global failure of our varnish cache layer. Our monitoring indicates that this issue began approximately 1027 UTC and traffic returned to normal levels around 1102 UTC.
This issue would have affected all applications on the Aspen and Bamboo application stacks as well as any applications with the ssl:ip addon as well as applications making use of the dedicated IP addresses that we publish for apex domains.
Category:
Heroku |
Comments OffJanuary 31, 2012, 2:28 am
08:00 AM GMT – 12:00 AM GMT – That time we have On-App software updated on those Clouds. Power action buttons can be disabled for VPSs in both Clouds.
