All Systems Operational

Uptime over the past 90 days. View historical uptime.
Astro Hosted Operational
90 days ago
99.97 % uptime
Today
Scheduling and Running DAGs and Tasks Operational
90 days ago
99.9 % uptime
Today
Deployment Access Operational
90 days ago
100.0 % 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
99.98 % uptime
Today
Dashboards and Analytics Operational
90 days ago
100.0 % uptime
Today
Astro Hybrid Operational
90 days ago
99.9 % uptime
Today
Scheduling and Running DAGs and Tasks Operational
90 days ago
99.9 % uptime
Today
Deployment Access Operational
Deployment Management Operational
Cloud UI Operational
Cloud API Operational
Cloud Image Repository Operational
Cluster Management Operational
Astro Observe 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.

Jul 2, 2025

No incidents reported today.

Jul 1, 2025
Astro CLI 1.35 may unintentionally modify worker queue configurations
Resolved - We’ve verified that all affected customers have been contacted regarding the issue with Astro CLI version 1.35.0.
Jul 1, 18:25 UTC
Update - Deploys using Astro CLI version 1.35 are now blocked to prevent unintentional changes to worker queues. Please use CLI version 1.34 or lower.
Jul 1, 16:55 UTC
Identified - We’ve identified the root cause of the issue in Astro CLI version 1.35 that results in unintentional modifications to worker queues. We have yanked Astro CLI 1.35.

Yanked release: https://github.com/astronomer/astro-cli/releases/tag/v1.35.0
Jul 1, 14:03 UTC
Investigating - Upgrading to Astro CLI version 1.35 can lead to unintended changes in your worker queues settings, particularly when deploying with modified or missing workerQueues definitions. Please use CLI version 1.34 or lower.
Jul 1, 13:59 UTC
Jun 30, 2025

No incidents reported.

Jun 29, 2025

No incidents reported.

Jun 28, 2025

No incidents reported.

Jun 27, 2025

No incidents reported.

Jun 26, 2025

No incidents reported.

Jun 25, 2025

No incidents reported.

Jun 24, 2025

No incidents reported.

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025

No incidents reported.

Jun 19, 2025
Brief Ingress Downtime on AWS Standard Clusters - us-east1
Completed - The scheduled maintenance has been completed.
Jun 19, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 19, 22:00 UTC
Scheduled - We will be performing a brief maintenance on our AWS infrastructure in the us-east-1 region for Standard (i.e. not Dedicated) clusters that may result in a ~1-minute disruption to incoming traffic. During this time, you may experience temporary unavailability of the Airflow UI, API, and image registry access, and failure of tasks.

This update improves platform performance and reliability, and is required for new planned feature work. No action is needed on your part.

Thank you for your understanding.
Jun 10, 16:31 UTC
Jun 18, 2025
Brief Ingress Downtime on AWS Standard Clusters - Most Regions
Completed - The scheduled maintenance has been completed.
Jun 18, 23:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 22:00 UTC
Scheduled - We will be performing a brief maintenance on our AWS infrastructure in the ap-southeast-1, eu-central-1, eu-west-1, and us-west-2 regions for Standard (i.e. not Dedicated) clusters that may result in a ~1-minute disruption to incoming traffic. During this time, you may experience temporary unavailability of the Airflow UI, API, and image registry access, and failure of tasks.

This update improves platform performance and reliability, and is required for new planned feature work. No action is needed on your part.

Thank you for your understanding.
Jun 10, 16:29 UTC
← Incident History Powered by Atlassian Statuspage