Engine Yard incident

AWS US-East-1 (N. Virginia) AZ issues impacting instances including EY platform instances

Major Resolved View vendor source →

Engine Yard experienced a major incident on December 22, 2021 affecting Engine Yard Cloud and ec2-us-east-1, lasting 12h 17m. The incident has been resolved; the full update timeline is below.

Started
Dec 22, 2021, 12:36 PM UTC
Resolved
Dec 23, 2021, 12:53 AM UTC
Duration
12h 17m
Detected by Pingoru
Dec 22, 2021, 12:36 PM UTC

Affected components

Engine Yard Cloudec2-us-east-1

Update timeline

  1. investigating Dec 22, 2021, 12:36 PM UTC

    We're seeing instance failures in one AZ in the N. Virginia AWS region. Customer environments and applications may be impacted by this at the current time. Engine Yard's own cloud.engineyard.com application has been impacted and at this time we are working on restoring service to this application. AWS have yet to official report any issues, but please monitor https://status.aws.amazon.com/ for updates.

  2. identified Dec 22, 2021, 01:23 PM UTC

    Functionality has now been restored to https://cloud.engineyard.com. AWS are seeing connectivity issues in one AZ in the US-East-1 (N. Virginia) region, which is causing instance reachability issues impacting both application functionality and instance control operations. Please open a ticket if you are having issues, and the issue can be monitored via https://status.aws.amazon.com/

  3. monitoring Dec 22, 2021, 04:17 PM UTC

    AWS have stabilised the impacted AZ and are restoring impacted instances. We are seeing the majority of impacted instances fully functional again. If you see any further issues please contact Support.

  4. resolved Dec 23, 2021, 12:53 AM UTC

    AWS has resolved the incident and we are not experiencing issues anymore. Please contact Support for any queries.