Increased Task Failures in US-East-1 (AWS) - AWS Incident
May 8, 07:43 UTCMay 9, 01:43 UTC
Duration
18h
Impact
Minor
Root cause
Not disclosed
Astronomer, 90 days
17 incidents
Affected
Not listed by the vendor.
Final update
AWS has confirmed recovery in the affected Availability Zone (use1-az4), and system performance has returned to normal levels. We are no longer observing elevated task failures or latency in the AWS us-east-1 region. Any previously impacted workloads should now be operating as expected. If you continue to experience issues, please reach out to Astronomer Support for assistance.
Timeline
- Resolved · May 9, 01:43 UTC
AWS has confirmed recovery in the affected Availability Zone (use1-az4), and system performance has returned to normal levels. We are no longer observing elevated task failures or latency in the AWS us-east-1 region. Any previously impacted workloads should now be operating as expected. If you continue to experience issues, please reach out to Astronomer Support for assistance.
- Monitoring · May 8, 07:45 UTC
We are continuing to monitor the situation as AWS works toward full recovery in the affected Availability Zone. At this time, we are seeing signs of stabilization, and most transient failures should continue to self-resolve. We will provide further updates once AWS confirms that the issue has been fully resolved.
- Investigating · May 8, 07:43 UTC
We are currently observing elevated task failures and latency for some deployments running in the AWS us-east-1 region. This is related to an ongoing AWS incident affecting a single Availability Zone (use1-az4), where EC2 and EBS resources have experienced impairments. What to expect: You may see intermittent task failures or retries in your deployments. In most cases, these failures are transient and should self-resolve automatically as AWS continues recovery. What you should do: No immediate action is required. However, if you notice consistent or prolonged failures, please reach out to Astronomer Support, and we’ll help investigate further. We are continuing to monitor the situation closely and will share updates as needed. Refer: https://health.aws.amazon.com/health/status
More from Astronomer
Full historyPHP Security Advisory: Astro and Astro Private Cloud Not Affected; Review Custom Imagesstill openSecurity Update: Runtime Releases and Guidance for the eMudhra/emSign Certificate Issuelasted 45h 27mDelayed delivery of Astro Alertslasted 26h 9mOrganization Dashboards are failing to load with Invalid kid parameter errorlasted 1h 23mAstro UI and API are appearing offline for some userslasted 1h 51mCapacity constraints in GCP us-central1 may delay or fail some task executionslasted 7d 21h