All Systems Operational
Uptime over the past 90 days. View historical uptime.
Astro Hosted Operational
90 days ago
99.96 % uptime
Today
Scheduling and Running DAGs and Tasks Operational
90 days ago
99.83 % uptime
Today
Deployment Access Operational
90 days ago
99.98 % uptime
Today
Deployment Management Operational
90 days ago
99.98 % uptime
Today
Cloud UI Operational
90 days ago
100.0 % uptime
Today
Cloud API Operational
90 days ago
100.0 % uptime
Today
Cloud Image Repository Operational
90 days ago
100.0 % uptime
Today
Astro Hybrid Operational
90 days ago
99.84 % uptime
Today
Scheduling and Running DAGs and Tasks Operational
90 days ago
99.84 % uptime
Today
Deployment Access Operational
Deployment Management Operational
Cloud UI Operational
Cloud API Operational
Cloud Image Repository Operational
Cluster Management Operational
Cloud IDE Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Past Incidents
Mar 16, 2025

No incidents reported today.

Mar 15, 2025

No incidents reported.

Mar 14, 2025
Service Degradation: Delayed or Missing DAG Alerts
Resolved - This incident has been resolved.
Mar 14, 12:51 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 14, 08:36 UTC
Identified - Our engineering team is actively investigating the root cause of this issue. We are working on implementing a long-term fix to restore full functionality. Further updates will be provided as we make progress.
Mar 14, 03:41 UTC
Investigating - Affected Services: Astro Alerts (DAG success, failure, SLA miss notifications)

Description: We are currently investigating an issue affecting DAG alerts on Astro.

Impact: Customers may experience delays or failures in receiving DAG alerts.
Mar 14, 03:39 UTC
Mar 13, 2025

No incidents reported.

Mar 12, 2025

No incidents reported.

Mar 11, 2025

No incidents reported.

Mar 10, 2025

No incidents reported.

Mar 9, 2025

No incidents reported.

Mar 8, 2025

No incidents reported.

Mar 7, 2025
Airflow DAGs cannot be triggered via the Astro UI
Resolved - This incident has been resolved.
Mar 7, 22:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 7, 22:20 UTC
Update - We are continuing to work on a fix for this issue.
Mar 7, 21:30 UTC
Identified - The issue has been identified and the fix is being implemented
Mar 7, 21:24 UTC
Airflow incorrectly being reported as being deployed
Resolved - The issue has been fixed and all deployment information is accurate.
Mar 7, 17:33 UTC
Identified - We have identified an issue where Airflow deployments are incorrectly being marked as being deployed. This causes the "Open Airflow" button in the Astro UI to be greyed out. Despite being greyed out, the "Open Airflow" button will still work, and the deployment is still able to be accessed. This does not affect the running Airflow deployments, so no DAGs will be affected.
Mar 7, 17:14 UTC
Mar 6, 2025

No incidents reported.

Mar 5, 2025

No incidents reported.

Mar 4, 2025
Deployment unhealthy after downgrading from Runtime 12.3.0+
Resolved - We are declaring an end to this incident as the impact has been determined to be quite narrow.

This issue will only impact a deployment that at one point was on an Astro Runtime version below 12.3.0, then upgraded to 12.3.0 - 12.7.1, upgraded again to a version between 12.3.0 - 12.7.1, then used the downgraded back to the initial 12.3.0 - 12.7.1 version. For example, if a Deployment were to go from 11.0.0 -> 12.3.0 -> 12.7.1 and attempt to rollback to 11.0.0, the rollback would be performed as expected, but if it was attempted to rollback to 12.3.0, it would fail.

We are working on an update to the Astro Data Plane to fix this issue which we expect to release this month. Our support team will assist if any deployments do encounter this bug in the meantime.
Mar 4, 19:50 UTC
Monitoring - The issue has been verified as a missed minor database update that does not impact deployment behaviour unless a deployment rollback is applied. A deployment is affected if it was upgraded to a Runtime version greater than 12.3.0 from a Runtime version lesser than 12.3.0.

For example:

- Runtime 12.2.0 upgraded to Runtime 12.7.0 (Affected)
- Runtime 12.0.0 upgraded to Runtime 12.3.0 (Affected)
- Runtime 12.4.0 upgraded to Runtime 12.7.0 (Unaffected)

The underlying issue has been fixed and any upgrades going forward is unaffected. We are currently applying a permanent fix for affected deployments.
Feb 28, 17:40 UTC
Investigating - Astronomer has identified an issue with the upgrade to Runtime 12.3.0+ where a database migration is not applied. While the upgrade will complete without errors, the deployment will become unhealthy when attempting to downgrade from Runtime 12.3.0+.

We do not recommend upgrading to Runtime 12.3.0+ at this time as there may be other incompatible interactions between the database.
Feb 28, 16:21 UTC
Mar 3, 2025

No incidents reported.

Mar 2, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage