Engine Yard
All Systems Operational
Engine Yard Cloud ? Operational
Help Center ? Operational
GitHub Operational
ec2-ap-northeast-1 Operational
ec2-ap-southeast-1 Operational
ec2-ap-southeast-2 Operational
ec2-eu-west-1 Operational
ec2-sa-east-1 Operational
ec2-us-east-1 Operational
ec2-us-west-1 Operational
ec2-us-west-2 Operational
Atlassian Bitbucket Git via HTTPS Operational
Atlassian Bitbucket SSH Operational
CloudFlare CloudFlare APIs Operational
CloudFlare SJC - San Jose, California, USA Operational
CloudFlare IAD - Ashburn, Virginia, USA Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 26, 2017

No incidents reported today.

Feb 25, 2017

No incidents reported.

Feb 24, 2017

No incidents reported.

Feb 23, 2017
Resolved - At this point we are considering this issue resolved and normal functionality has been restored. If you have any questions or want to discuss, please file a ticket and we are happy to assist
Feb 23, 21:34 UTC
Monitoring - AWS has reported that they have resolved the underlying issue and the majority of EBS volumes should now be working with the rest repaired shortly. We are continuing to monitor the situation. If you have any questions or want to discuss, please file a ticket and we are happy to assist
Feb 23, 20:45 UTC
Identified - AWS has reported degraded performance on a small number of EBS volumes in the us-east region. AWS is currently working on correcting this issue. If you have any questions or want to discuss, please file a ticket and we are happy to assist
Feb 23, 20:17 UTC
Feb 22, 2017

No incidents reported.

Feb 21, 2017

No incidents reported.

Feb 20, 2017

No incidents reported.

Feb 19, 2017

No incidents reported.

Feb 18, 2017

No incidents reported.

Feb 17, 2017
Resolved - This incident has been resolved.
Feb 17, 02:50 UTC
Monitoring - Between 3:23 AM UTC and 3:42 AM UTC, our system generated old StatusCheck alerts for some instances. These are real alerts but were only delivered today due to an issue on our end which we have already fixed. The alerts affected are StatusCheckFailed_Instance, StatusCheckFailed_System, and CpuCreditBalance. The last one is only for T2 instances.

In most cases, the alerts were automatically resolved and no action is needed on your part. If you see an alert that is not resolved, please check that you can ssh to the instance.

If you have any questions, please log in to your account to file a ticket.
Feb 16, 04:30 UTC
Feb 15, 2017

No incidents reported.

Feb 14, 2017

No incidents reported.

Feb 13, 2017

No incidents reported.

Feb 12, 2017

No incidents reported.