Astronomer

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:40 UTC

   We are investigating an issue where Astro Alerts notifications may be delayed for some customers. Our team is actively working to resolve the issue, and we will provide an update as soon as we have more information.

2. identified 2026-10-20 07:55 UTC

   We have identified the cause and are rolling out a fix to the affected deployments. Alerts held during the incident have started to be delivered, and some alerts may continue to be delayed until the rollout is complete. We will provide another update once the fix is fully rolled...

3. identified 2026-10-20 10:42 UTC

   The fix has been applied to the majority of affected deployments, and delayed alerts continue to be delivered as we process the backlog. We are addressing a small number of remaining deployments and will provide another update once this is complete.

4. monitoring 2026-10-20 12:38 UTC

   The backlog of delayed Astro Alerts has been fully processed, and we are monitoring recovery following the fix. A small number of alerts may still be briefly delayed as the fix completes on remaining systems.

5. resolved 2026-10-21 08:49 UTC

   Astro Alerts delivery has returned to normal, and this incident is resolved. We have applied the fix and fully processed the backlog of delayed alerts. Thank you for your patience while we worked to restore service.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 09:37 UTC

   We are currently investigating this issue. We will keep this page updated as we have more information.

2. identified 2026-10-19 10:28 UTC

   We have identified the source of the issue and are actively working on a fix. We’ll share further updates as we make progress.

3. resolved 2026-10-19 11:00 UTC

   The issue has been resolved, and the Organization Dashboards are now working as expected.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-13 18:02 UTC

   The Astro Core API is showing an elevated number of errors. We are investigating actively and will update as soon as we know more. Next update will be within the next 30 minutes.

2. investigating 2026-10-13 18:13 UTC

   Our metrics indicate no impact on existing tasks and Dag Runs. They are continuing to run successfully. We are continuing to investigate what is causing the API and UI errors and are attempting a workaround.

3. monitoring 2026-10-13 18:28 UTC

   We have restarted one of our services that was experiencing higher than expected load. This has returned the Astro UI and API to functionality. We are continuing to investigate root cause.

4. resolved 2026-10-13 19:53 UTC

   We have identified the proximate cause of the incident and are confident that the situation is stable. We will follow up with more detail in a postmortem at a later date.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-06 03:33 UTC

   We are currently seeing a capacity shortage in the Google Cloud (GCP) `us-central1` region. As a result, some Deployments running in this region may experience delays when scaling up worker nodes and pods. Some tasks may remain in a queued state for longer than usual while...

2. resolved 2026-10-14 00:34 UTC

   We have seen improved capacity in the GCP us-central1 region across additional machine types, and error rates for worker node and pod scale-up have dropped. If any tasks failed during this incident, you can clear and rerun them. To recover automatically from future capacity...

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-10-03 20:42 UTC

   We have identified a recent change that broke the templating of the deploymentId and workspaceId fields used in the Astro Alert emails for Dag Success and Failure emails. We are working on a fix and will provide updates shortly.

2. identified 2026-10-03 21:03 UTC

   Correction: Deployment and Workspace _names_ are not populated, earlier update cited IDs incorrectly.

3. monitoring 2026-10-03 21:13 UTC

   We have reverted the problematic email template changes and are continuing to monitor for full resolution.

4. resolved 2026-10-03 21:39 UTC

   All Astro Alert emails for Dag Success/Failure now correctly include the deployment/workspace name.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 22:40 UTC

   We have identified several hosted deployments where tasks are getting stuck in the queued state and failing. This is happening the worker autoscaler is having issues with scaling up workers to run tasks. We are investigating the cause of this.

2. resolved 2026-10-01 23:47 UTC

   Our development team has concluded that this was a false alert. It is not affecting multiple deployments.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-24 14:52 UTC

   We are investigation reports that the Deployments view of the Astro Cloud UI is unavailable. We will update as we know more.

2. investigating 2026-09-24 14:56 UTC

   We have confirmed that task execution is unaffected. We're continuing to investigate.

3. monitoring 2026-09-24 15:19 UTC

   We have rolled back an identified breaking change, and are beginning to see error rates decrease. Please refresh the Astro Cloud UI in your browser.

4. resolved 2026-09-24 15:34 UTC

   Issue has been resolved and error rates have returned to baseline. If you are still experiencing issues please refresh the page, and open a support ticket if that does not resolve the issue.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-17 17:54 UTC

   We have identified a regression affecting custom roles due to a change rolled out today. This resulted in permissions being dropped from custom roles silently. We have received reports of deploys linked to tokens using custom roles not working. Until the fix has been rolled out,...

2. monitoring 2026-09-17 19:29 UTC

   All custom roles have been restored to their previous functionality and full operation has been restored.

3. resolved 2026-09-17 21:50 UTC

   No further issues have been found, so this is being marked as resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-09-08 12:33 UTC

   We have identified the cause. On Astro, each worker queue is backed by a Kubernetes autoscaling resource whose name is built from a fixed platform prefix, the deployment release name, and the worker queue name. For a very small number of customers, where that combined name...

2. monitoring 2026-09-08 19:42 UTC

   A fix has been implemented, and we are monitoring the results.

3. resolved 2026-09-08 20:09 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-04 03:08 UTC

   We are currently investigating an issue affecting deployment access, authentication, and related services for multiple customers. Some users may experience 401 errors when using organization-based Astronomer URLs (ORG_ID.astronomer.run), as well as "RBAC: access denied" errors...

2. investigating 2026-09-04 04:28 UTC

   We're continuing to investigate the issue affecting access/auth to some deployments and services. We will follow up with an update no later than 5:30 AM UTC on Friday, September 4, 2026, or sooner if we have something to share.

3. identified 2026-09-04 04:52 UTC

   The potential root cause identified, and fix is underway

4. monitoring 2026-09-04 05:53 UTC

   We identified and resolved an infrastructure configuration issue that was causing authentication failures and deployment access errors across the platform. The root cause was a network configuration change during an infrastructure upgrade that temporarily disrupted connectivity...

5. resolved 2026-09-04 06:07 UTC

   The issue has been fully resolved. All services, including authentication, deployment access, and DAG visibility, are operating normally. We apologize for the disruption and thank you for your patience.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

Started during Google Cloud: Multiple products in us-central1-b are experiencing network service degradation..

1. investigating 2026-09-01 18:40 UTC

   We are currently investigating a Google Cloud networking incident that may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow deployments. For more...

2. investigating 2026-09-01 18:43 UTC

   We are currently investigating a Google Cloud networking incident that began around 16:03 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from...

3. investigating 2026-09-01 18:44 UTC

   We are currently investigating a Google Cloud networking incident that began around 16:03 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from...

4. investigating 2026-09-01 19:05 UTC

   We are investigating a Google Cloud networking incident that began around 14:41 UTC and may affect Astro deployments running in the us-central1 region. Customers may see intermittent networking connectivity disruptions, DNS resolution errors, or missing metrics from Airflow...

5. monitoring 2026-09-01 19:19 UTC

   Google Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC. During this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution...

6. monitoring 2026-09-01 20:42 UTC

   Google Cloud has resolved the networking incident affecting us-central1. The incident ran from approximately 14:44 UTC to 18:52 UTC. During this period, some Astro deployments in us-central1 may have experienced intermittent networking connectivity disruptions, DNS resolution...

7. resolved 2026-09-01 22:29 UTC

   The GCP incident is marked as Closed officially

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 18:51 UTC

   Our metrics pipeline is falsely displaying spikes in scheduler heartbeat metrics, despite underlying component health.

2. identified 2026-09-08 18:31 UTC

   We've identified the cause of the false availability alerts that have been showing the Astro UI. This is a degradation affecting dashboard and monitoring visibility only. Task execution, scheduling, and workflow processing have not been impacted. The issue is the result of a...

3. resolved 2026-09-10 22:19 UTC

   This issue is now resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-18 04:17 UTC

   We have identified an issue affecting an internal rollout related to the `pre_execute` Airflow hook in Astro Hosted. We have identified a fix and are rolling it out across the fleet. We are monitoring the rollout and will provide further updates as it progresses.

2. monitoring 2026-08-18 04:18 UTC

   Fix is being rolled out across all astro deployments.

3. resolved 2026-08-18 07:36 UTC

   Rollout has been completed

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-04 15:11 UTC

   We've identified a change that enabled GPU support for KubernetesPodOperator pods had an unintended side effect when reading pod specs without proper limits set in the expected format. We're working on a fix, if you notice any unexpected failures for KPO tasks in your Astro...

2. monitoring 2026-08-04 15:15 UTC

   We have rolled back the changes that triggered this issue and are monitoring the issue for confirmation that this issue is resolved.

3. resolved 2026-08-04 16:40 UTC

   Mitigations have been successful. A Platform release that corrects this errant behavior is being worked on now. Issue is resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-08-04 12:57 UTC

   We are investigating intermittent connectivity issues affecting clusters in Azure Central US when calling Astronomer APIs. This may prevent or delay attempts to create, update, or delete Airflow Deployments. Our engineering team is actively investigating the issue and working to...

2. monitoring 2026-08-04 13:34 UTC

   Affected clusters have recovered and are operating normally. We are continuing to monitor the environment to ensure service stability.

3. resolved 2026-08-04 14:36 UTC

   This interruption has been resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 16:02 UTC

   We are currently investigating an issue with platform log ingestion for Astro. Logs may not be available in the Cloud UI.

2. investigating 2026-07-30 16:33 UTC

   We are continuing to investigate this issue, and will provide another update in 30mins or as new information is available.

3. identified 2026-07-30 18:03 UTC

   We have identified the source of increased log generation volume, which is causing issues on the ingestion side. We're implementing mitigations now and are monitoring the results.

4. identified 2026-07-30 18:43 UTC

   We are continuing to investigate and monitor this issue.

5. monitoring 2026-07-30 19:06 UTC

   We are beginning to see ingestion catch up with backlog log load. Customers may begin to see some logs becoming available in the Cloud UI

6. monitoring 2026-07-30 20:05 UTC

   We continue to see log ingestion improving on the platform, and we're continuing to monitor the situation.

7. monitoring 2026-07-30 21:47 UTC

   We are continuing to see progress as the log injestions works through the backlog. Available logs are now about ~20mins old, and we expect to see that latency return to normal baseline in the next 2 hours.

8. resolved 2026-07-30 22:38 UTC

   Ingestion lag is back at baseline

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-07-07 22:18 UTC

   We have detected node scaling issues in the Azure EastUS2 region and are currently investigating.

2. monitoring 2026-07-07 22:46 UTC

   Engineers observe that affected clusters are returning to "healthy" status.

3. resolved 2026-07-07 22:47 UTC

   The incident is fully resolved and all Azure clusters in EastUS2 are functioning as expected.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-07-06 11:35 UTC

   We are investigating node scaling issues in the AWS us-east-1 region. Customers may experience issues with worker scale-up and new task startup.

2. investigating 2026-07-06 13:00 UTC

   AWS has published a status update for this issue. We are actively monitoring their progress and will continue to share updates.

3. monitoring 2026-07-06 14:24 UTC

   AWS has now acknowledged a us-east-1 EC2 Launch Template API incident impacting EKS node provisioning/scaling (incl. Karpenter). We are continuing to monitor the situation.

4. monitoring 2026-07-06 15:00 UTC

   We are no longer seeing any impacting clusters in the AWS us-east-1 region. We're continuing to monitor the situation.

5. resolved 2026-07-06 16:06 UTC

   AWS has confirmed this incident is resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-06-15 23:27 UTC

   We are currently investigating this issue.

2. identified 2026-06-15 23:28 UTC

   **The issue, according to Azure status page** Investigating a spike in 401 authentication errors We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We've identified a potential underlying factor related to a...

3. monitoring 2026-06-15 23:34 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-06-16 00:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-15 16:23 UTC

   We've identified an issue with `astro deploy`s not updating manifests in Astro Hosted clusters, and we're currently applying a workaround and are continuing to monitor the situation.

2. monitoring 2026-06-15 16:54 UTC

   We are monitoring the affect of the applied fix and are observing error rates coming down/ceasing for affected clusters.

3. resolved 2026-06-15 17:51 UTC

   Mitigation was effective and all affected clusters are healthy.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 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...

2. monitoring 2026-05-08 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...

3. resolved 2026-05-09 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...

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-07 10:31 UTC

   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...

2. identified 2026-05-07 11:15 UTC

   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.

3. identified 2026-05-07 12:57 UTC

   A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway.

4. monitoring 2026-05-07 13:49 UTC

   A fix has been implemented, and we are monitoring the results.

5. resolved 2026-05-07 14:24 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-06 19:56 UTC

   Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.

2. resolved 2026-05-06 20:05 UTC

   Our team has determined this only affects internal access, Astro end users are unaffected.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-04 10:56 UTC

   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...

2. investigating 2026-05-04 10:56 UTC

   We are continuing to investigate this issue.

3. resolved 2026-05-04 20:15 UTC

   This incident is now resolved, and all Cost Breakdown data is now up to date. The issue that caused the delay has been fixed and should not recur.

Excerpts are shortened. Read the full incident on Astronomer's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-04-27 22:04 UTC

   It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.

2. investigating 2026-04-27 22:05 UTC

   We are continuing to investigate this issue.

3. resolved 2026-04-28 00:16 UTC

   We rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found their 403s resolved themselves after some time.

Excerpts are shortened. Read the full incident on Astronomer's status page.