Instability in us-east-1

Summary

Instability in us-east-1

An upstream AWS issue affected infrastructure in a single Availability Zone in us-east-1. During the event, we blocked provisioning into the affected zone and monitored AWS’s recovery efforts. AWS has since recovered enough of the affected availability zone for the impacted Aptible infrastructure to recover. We have also completed recovery of any Aptible-managed resources that required follow-up action on our side. Any customers with directly affected resources have been notified of resolution. We are continuing normal platform monitoring, but we are marking this incident as resolved on our end.

• Started

  May 7, 2026 · 9:05 PM

• Resolved

  May 8, 2026 · 11:35 PM

• Duration

  1d 2h 30m

• Severity

  None

• ◐

  Investigating

  May 7 · 9:05 PM Aptible

  Due to an underlying issue in AWS we are experiencing instability in a certain availability zone in us-east-1. We are investigating this issue and will follow up with recommendations shortly

• ◆

  Identified

  May 7 · 9:39 PM Aptible

  We have blocked operations from provisioning into the specified availability zone

• ◉

  Monitoring

  May 8 · 10:02 AM Aptible

  We have unblocked operations from the specified region as we have seen successful provisioning and maintenance of new instance in that availability zone. Instances that were affected have not yet seen recovery, and the upstream AWS alert indicates they may still take hours of recovery.

• ✓

  Resolved

  May 8 · 11:35 PM Aptible

  An upstream AWS issue affected infrastructure in a single Availability Zone in us-east-1. During the event, we blocked provisioning into the affected zone and monitored AWS’s recovery efforts. AWS has since recovered enough of the affected availability zone for the impacted Aptible infrastructure to recover. We have also completed recovery of any Aptible-managed resources that required follow-up action on our side. Any customers with directly affected resources have been notified of resolution. We are continuing normal platform monitoring, but we are marking this incident as resolved on our end.