This is an Acquia Service Alert to all Acquia subscribers.
Update - 2:10p ET
The Acquia Network is now accessible and normal operations are restored, except for access to the Acquia Library. We will continue to monitor for additional issues and will alert you if any occur.
This was obviously a major event. We will follow up with further details about what happened and what actions we are taking to mitigate against future such outages after we review the situation and put a plan in place.
Thank you for your patience and we apologize for the inconvenience.
Update - 12:40p ET
We continue to work with Amazon on resolving the service interruption. As of this point the situation is not resolved. Ongoing details are available on Amazon's status site at http://status.aws.amazon.com/.
A restoration of the Acquia Network to an alternate data center is in progress.
Technical note: Some customers running the Acquia Connector module may have experienced *cron failures due to the Acquia Connector timing out on RPC calls back to the Acquia Network during each cron run. We have partially restored the RPC service and RPC calls will no longer time out. Any site where cron was being interrupted for this reason should now run uninterrupted.
*cron is a background process which performs various maintenance task such as updating indexes.
Update - 10:55a ET:
We continue to work with Amazon resolving the service interruption. Further details are available on Amazon's status site. http://status.aws.amazon.com/
We are attempting to bring network.acquia.com up in an alternate AWS data center and will provide regular updates until the issue is resolved.
Due to ongoing issues at an Amazon Web Services data center, the Acquia Network and related services such as the ticketing system, Acquia Cloud interface, and knowledge base are temporarily unavailable.
Acquia is following Amazon's efforts to correct the situation.
We apologize for the inconvenience and will send out an alert when the Amazon issues are resolved and access to the Acquia Network is restored.