Astronomer incident
Capacity constraints in GCP us-central1 may delay or fail some task executions
Resolved after 7 days 21 hours, on October 6, 2026.
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 constraints, we recommend setting `retries` and `retry_delay` on your tasks or in `default_args`. If you’re still seeing issues, please contact Astronomer Support.
Update timeline
- investigating Oct 06, 2026, 03:33 AM 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 waiting for compute capacity. In some cases, tasks that stay queued beyond their configured timeout may fail. **Recommended workaround:** Configuring automated task retries (for example, setting `retries` and a `retry_delay` on your tasks or in your DAG's `default_args`) will help tasks recover automatically once capacity becomes available. We are working to address the issue and keep this page posted as we have more updates.
- resolved Oct 14, 2026, 12:34 AM 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 constraints, we recommend setting `retries` and `retry_delay` on your tasks or in `default_args`. If you’re still seeing issues, please contact Astronomer Support.
Your product runs on more than Astronomer
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services