Astronomer Outage History
Uptime record, past incidents, and downtime history for Astronomer.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| May 2026 | 80% | 25 | 5 |
| April 2026 | 70% | 30 | 9 |
| March 2026 | 90.3% | 31 | 3 |
| February 2026 | 60% | 5 | 2 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 91 Days)
Feb 24
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
May 2026
Increased Task Failures in US-East-1 (AWS) - AWS Incident
Started: May 8, 7:43 AM
monitoring
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.
May 8, 7:45 AM
investigating
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 immedi...
May 8, 7:43 AM
Delayed delivery for some time-based alerts
Started: May 7, 10:31 AM
monitoring
A fix has been implemented, and we are monitoring the results.
May 7, 1:49 PM
identified
A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway.
May 7, 12:57 PM
identified
We have identified the cause of the delayed delivery for some time-based alerts and are implementing a fix. We will provide another update once the fix has been deployed and validated.
May 7, 11:15 AM
investigating
We are investigating delayed delivery for some time-based alerts. The delay is primarily visible for DAG Timeliness alerts, and may also affect Observe-related SLA, Proactive SLA, and Data Quality monitor alerts. DAG Duration and Task Duration alerts do not appear to be affected at this time.
May 7, 10:31 AM
Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.
Started: May 6, 7:56 PM
investigating
Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.
May 6, 7:56 PM
Dashboard cost breakdown data delays
Started: May 4, 10:56 AM
investigating
We are continuing to investigate this issue.
May 4, 10:56 AM
investigating
We’re investigating an issue affecting Dashboard cost breakdown data. For affected customers, cost breakdown information may appear stale and may not have updated since May 1, 2026. Our team is actively investigating the cause and working to restore current data. We’ll share another update as we have more information.
May 4, 10:56 AM
April 2026
Airflow UI showing 403s for some customers
Started: Apr 27, 10:04 PM
investigating
We are continuing to investigate this issue.
Apr 27, 10:05 PM
investigating
It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.
Apr 27, 10:04 PM
Azure East US multiservice outage impacting Astro deployments in the region
Started: Apr 24, 5:28 PM
monitoring
Azure has fixed the issue, and services are back to normal in East US. We are monitoring to make sure everything stays stable.
Apr 25, 3:56 AM
identified
Azure East US has reported multi-service impact that is affecting Astro deployments in the region. For more information on Azure outage, please visit: https://azure.status.microsoft/en-us/status
Apr 24, 5:28 PM
Terminating Workers Accepting Tasks Causing Failures in Astro Executor
Started: Apr 17, 8:04 AM
monitoring
The fix has been implemented, and we are now monitoring the deployments.
Apr 17, 10:01 AM
identified
We have identified the issue and we are rolling out the fix for the affected deployments.
Apr 17, 8:05 AM
investigating
We have identified an issue with Astro Executor deployments where terminating workers can continue to accept new tasks, which can, in some cases, can cause these tasks to fail.
Apr 17, 8:04 AM
Runtime 3.2-1 Yanked - Incompatible with Env Manager
Started: Apr 16, 6:04 PM
identified
We have identified that Runtime 3.2-1 is incompatible with the Astro Environment Manager. Any Connections or Variables stored at the Workspace level will not be available on deployments running 3.2-1. For this reason, we have disallowed the use of 3.2-1 for any deployments which are not already on that version. We are working to release a 3.2-2 version that is properly compatible as quickly as possible.
Apr 16, 6:04 PM
Degraded service for some deployments in Azure West Europe
Started: Apr 13, 9:44 PM
identified
We are currently investigating an issue affecting deployments in our Azure West Europe region. Some customer deployments are experiencing degraded performance due to a compute resource constraint in our shared infrastructure.
Our engineering team has identified that the region has reached its vCPU quota limit for a specific compute type, which is preventing new resources from being provisioned. We have opened a high-priority support request with Azure to increase this quota and are activel...
Apr 13, 9:44 PM
Astro Alerts Degraded Performance
Started: Apr 12, 10:56 PM
monitoring
We have applied a fix for the Astro Alerts degraded performance and currently monitoring it.
Apr 13, 12:40 AM
identified
We have identified the issue with Astro Alert's degraded performance and currently working on a fix.
Apr 13, 12:18 AM
investigating
We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.
Apr 12, 10:56 PM
Deployment changes fail due to an unrelated "hibernation" error
Started: Apr 1, 6:31 PM
identified
We are continuing to work on a fix for this issue.
Apr 1, 6:32 PM
identified
The issue has been identified and a fix is being implemented.
Apr 1, 6:31 PM