Is Astronomer down?
Last checked 10m agoNo incidents right now.
Astronomer is operational right now. Last checked 10m ago; the most recent incident resolved 6d ago.
Real-time Astronomer status, recent outages, and incident history — pulled directly from Astronomer's official status page at https://status.astronomer.io every 5 minutes. Pingoru tracks 15 Astronomer services and has captured 10 incidents in the last 90 days (99.19% uptime). Get email, Slack, Discord, or webhook alerts the moment Astronomer reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 3 updates
- identified · Sep 08, 2026, 12:33 PM 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 exceeds the Kubernetes 63-character limit, the autoscaling resource is rejected at creation. As a result, workers do not scale for the affected queue and tasks routed there remain in the queued state. This is why the limit can be reached even when the worker queue name itself looks short: the release name and platform prefix already consume a large portion of the 63 characters before the queue name is appended. Workaround: If affected, until the permanent fix is deployed, please keep worker queue name at or below 10 characters. We are preparing a permanent fix. Further updates to follow.
- monitoring · Sep 08, 2026, 07:42 PM UTC
A fix has been implemented, and we are monitoring the results.
- resolved · Sep 08, 2026, 08:09 PM UTC
The incident has been resolved.
Latest: The incident has been resolved.
-
-
Timeline · 5 updates
- investigating · Sep 04, 2026, 03:08 AM 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 or difficulty viewing DAGs in the Astronomer UI.
- investigating · Sep 04, 2026, 04:28 AM 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.
- identified · Sep 04, 2026, 04:52 AM UTC
The potential root cause identified, and fix is underway
- monitoring · Sep 04, 2026, 05:53 AM 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 between our control plane and customer deployments. The fix has been applied and initial validation confirms services are recovering We are actively monitoring to confirm full recovery across all affected deployments. If you are still experiencing issues, please contact support.
- resolved · Sep 04, 2026, 06:07 AM 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.
Latest: 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 …
-
-
Timeline · 7 updates
- investigating · Sep 01, 2026, 06:40 PM 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 information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
- investigating · Sep 01, 2026, 06:43 PM 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 Airflow deployments. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
- investigating · Sep 01, 2026, 06:44 PM 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 Airflow deployments. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
- investigating · Sep 01, 2026, 07:05 PM 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 deployments. For more information, see the [Google Cloud status incident](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "Google Cloud status incident").
- monitoring · Sep 01, 2026, 07:19 PM 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 errors, or missing metrics from Airflow deployments.
- monitoring · Sep 01, 2026, 08:42 PM 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 errors, or missing metrics from Airflow deployments. This issue has since been resolved by Google, but we are continuing to monitor the situation internally to ensure it's resolution.
- resolved · Sep 01, 2026, 10:29 PM UTC
The GCP incident is marked as Closed officially
Latest: The GCP incident is marked as Closed officially
-
-
Timeline · 3 updates
- investigating · Aug 18, 2026, 06:51 PM UTC
Our metrics pipeline is falsely displaying spikes in scheduler heartbeat metrics, despite underlying component health.
- identified · Sep 08, 2026, 06:31 PM 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 metrics reporting bug that has been intermittently flagging scheduler heartbeats as missed when they were not. We are actively rolling out a fix that corrects how these metrics are reported.
- resolved · Sep 10, 2026, 10:19 PM UTC
This issue is now resolved.
Latest: This issue is now resolved.
-
-
Timeline · 3 updates
- investigating · Aug 18, 2026, 04:17 AM 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.
- monitoring · Aug 18, 2026, 04:18 AM UTC
Fix is being rolled out across all astro deployments.
- resolved · Aug 18, 2026, 07:36 AM UTC
Rollout has been completed
Latest: Rollout has been completed
-
See the full Astronomer outage history
5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Astronomer outage history →Or sign up free to get alerts when Astronomer breaks · 10 free monitors · No credit card
- Started Sep 08, 2026, 12:33 PM UTC · Resolved Sep 08, 2026, 08:09 PM UTC · 7h 35m
- Increased auth errors ResolvedStarted Sep 04, 2026, 03:08 AM UTC · Resolved Sep 04, 2026, 06:07 AM UTC · 2h 58m
- Started Sep 01, 2026, 06:40 PM UTC · Resolved Sep 01, 2026, 10:29 PM UTC · 3h 49m
- Started Aug 18, 2026, 06:51 PM UTC · Resolved Sep 10, 2026, 10:19 PM UTC · 23d 3h
- Started Aug 18, 2026, 04:17 AM UTC · Resolved Aug 18, 2026, 07:36 AM UTC · 3h 18m
- Started Aug 04, 2026, 03:11 PM UTC · Resolved Aug 04, 2026, 04:40 PM UTC · 1h 29m
- Started Aug 04, 2026, 12:57 PM UTC · Resolved Aug 04, 2026, 02:36 PM UTC · 1h 38m
- Platform Log ingestion issue ResolvedStarted Jul 30, 2026, 04:02 PM UTC · Resolved Jul 30, 2026, 10:38 PM UTC · 6h 35m