Engine Yard incident

Inhability to boot and/or configure instances

Notice Resolved View vendor source →

Engine Yard experienced a notice incident on July 3, 2019 affecting Engine Yard Cloud, lasting —. The incident has been resolved; the full update timeline is below.

Started
Jul 03, 2019, 06:19 PM UTC
Resolved
Jul 03, 2019, 06:19 PM UTC
Duration
Detected by Pingoru
Jul 03, 2019, 06:19 PM UTC

Affected components

Engine Yard Cloud

Update timeline

  1. resolved Jul 03, 2019, 06:19 PM UTC

    On July 3, 2019 at 17:12:45 GMT, our monitoring system alerted that a core component of the platform was not responding. This component is responsible of providing information on stack versions and access to Chef recipes used to configure instances. At 17:20:05 GMT it was identified that the application running this component couldn't connect to the database. At 17:21:15 GMT it was detected that the db instance had restarted itself and was entering recovery mode. At 17:30:54 GMT the component resumed services. At 17:54:33 GMT, after both automatic and manual testing reported no failures, the issue was deemed as solved.