Engine Yard incident

Amazon has notified of an Emergency change in the reboot schedule. Instances requiring reboots will restart by 6:00 AM Pacific tomorrow.

Notice Resolved View vendor source →

Engine Yard experienced a notice incident on January 3, 2018, lasting 2d 7h. The incident has been resolved; the full update timeline is below.

Started
Jan 03, 2018, 11:53 PM UTC
Resolved
Jan 06, 2018, 07:13 AM UTC
Duration
2d 7h
Detected by Pingoru
Jan 03, 2018, 11:53 PM UTC

Update timeline

  1. identified Jan 03, 2018, 11:53 PM UTC

    Engine Yard Support is adjusting team member schedules to provide additional staffing to assist with the anticipated influx of Support requests tonight and tomorrow morning, and will be doing everything possible to try to minimize the impact of this event upon your applications. If you have already completed your restarts or reboots this should not affect you. If you need to verify the instances impacted you can visit https://cloud.engineyard.com/instance-reboots We encourage you to try and restart or replace instances to the extent possible prior to this maintenance.

  2. resolved Jan 06, 2018, 07:13 AM UTC

    Amazon has rolled out security patches to their infrastructure designed to address recently announced hardware security vulnerabilities; this rollout completed January 4th. This update is known to create CPU performance concerns, especially for legacy instance types. Current workarounds include upgrading to Gen4 instances, tuning & optimization, and scaling of hardware.