Looking for an update now? Check the current status, or follow Astronomer for future changes.
43.9%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
60%
30
12
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
19 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.
Dashboard cost breakdown data delays
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
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.
April 2026
Airflow UI showing 403s for some customers
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are continuing to investigate this issue.
investigating
It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.
Azure East US multiservice outage impacting Astro deployments in the region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Azure has fixed the issue, and services are back to normal in East US. We are monitoring to make sure everything stays stable.
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
Terminating Workers Accepting Tasks Causing Failures in Astro Executor
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The fix has been implemented, and we are now monitoring the deployments.
identified
We have identified the issue and we are rolling out the fix for the affected deployments.
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.
Runtime 3.2-1 Yanked - Incompatible with Env Manager
majorSource not attested
Last archived state: resolved
View archived record details
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.
Degraded service for some deployments in Azure West Europe
Source not attested
Last archived state: resolved
View archived record details
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...
Astro Alerts Degraded Performance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have applied a fix for the Astro Alerts degraded performance and currently monitoring it.
identified
We have identified the issue with Astro Alert's degraded performance and currently working on a fix.
investigating
We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.
Deployment changes fail due to an unrelated "hibernation" error
majorSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix is being implemented.
