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.

Scope: Astro Hosted, including Remote Execution

Scheduled maintenance to improve Astro’s platform performance and reliability will begin at 10 AM EST and is expected to last approximately three hours.

Expected impact

• The Astro UI, IDE, Otto, Observability UI, Astro API, and Airflow UI will be unavailable. Please plan for the Airflow UI to be inaccessible throughout the window.

• DAGs and tasks will continue running, except those that depend on the affected APIs. API-triggered DAG runs may also be disrupted.

• Private connectivity will remain uninterrupted.

• Observability and Lineage ingestion is expected to continue, with any delayed data catching up afterward.

Preparation

If you require Airflow API access, review, configure, and test a Direct Access Token before maintenance. Direct Access Tokens bypass organization-level IP restrictions; confirm this meets your security requirements. They do not restore Astro API or Airflow UI access.

Updates will be posted here throughout the maintenance. Please contact your Account Team if you need help preparing.

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

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.

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.

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

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

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.

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

This issue is now resolved.

The incident has been resolved.

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.

The GCP incident is marked as Closed officially

Rollout has been completed

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

This interruption has been resolved.

Ingestion lag is back at baseline