Astronomer has postponed the scheduled maintenance that was planned for today, Saturday, November 7, 2026, at 10 AM EST.

Early this morning, our cloud provider detected a health event and automatically failed over our primary database, which interrupted the database replication that the maintenance depends on. As a result, Astronomer has postponed the maintenance. The new maintenance date will be shared as soon as it is planned; it will be no sooner than early 2027.

We can confirm that no PHP components are included in Astro.

We have now released updated agent client patches for use in Remote Execution deployments that incorporate certificate trust updates to mitigate the vulnerability. These are 1.8.11, 1.7.7, and 1.6.5. See more details in the Agent Release Notes.

Additionally, we have released another update of the Runtime images to handle the following two changes related to this vulnerability.

• New virtual environments created with python -m venv now get pip 26.2.2

• Upgrade grpcio to 1.84.1, whose bundled CA list no longer includes the roots affected by the eMudhra compromise

The following Runtime image versions include these changes. For more details see Runtime Release Notes.

• Runtime 13: 13.12.2

• Runtime 3.0: 3.0-21

• Runtime 3.1: 3.1-24

• Runtime 3.2: 3.2-13

• Runtime 3.3: 3.3-11

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.

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