Skeddly incident

Increased AWS API Error Rates in us-east-1

Minor Resolved View vendor source →

Skeddly experienced a minor incident on December 13, 2016, lasting 1h 17m. The incident has been resolved; the full update timeline is below.

Started
Dec 13, 2016, 05:12 AM UTC
Resolved
Dec 13, 2016, 06:29 AM UTC
Duration
1h 17m
Detected by Pingoru
Dec 13, 2016, 05:12 AM UTC

Update timeline

  1. identified Dec 13, 2016, 05:31 AM UTC

    Starting at 4:50am UTC on December 13, 2016, AWS was responding with many "InternalError" error codes during EC2 API calls in the us-east-1 (US Virginia) region. Skeddly is mitigating the errors where possible, but in many cases, actions are failing.

  2. identified Dec 13, 2016, 05:34 AM UTC

    AWS is now reporting the following on the AWS status page, http://status.aws.amazon.com/ "We are currently investigating elevated error rates for EBS-related APIs. Currently running instances and volumes are operating normally."

  3. resolved Dec 13, 2016, 06:29 AM UTC

    The AWS API errors have been resolved: "Between 8:16 PM and 9:50 PM PST, EBS-related APIs experienced elevated failure rates. Customers experienced errors modifying and describing volumes and snapshots. Existing running EC2 instances and EBS volumes were unaffected. The issue has been resolved and the service is operating normally."