All Systems Operational

Uptime over the past 90 days. View historical uptime.
Astro Hosted Operational
90 days ago
99.94 % uptime
Today
Scheduling and Running DAGs and Tasks Operational
90 days ago
99.89 % uptime
Today
Deployment Access Operational
90 days ago
99.98 % uptime
Today
Deployment Management Operational
90 days ago
99.97 % uptime
Today
Cloud UI Operational
90 days ago
99.87 % uptime
Today
Cloud API Operational
90 days ago
99.93 % 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
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.

May 21, 2025

No incidents reported today.

May 20, 2025
403 Errors for Image Deploys
Resolved - We have determined that this error is caused by cached credentials which are no longer valid after an internal change in Astro to the image registry. The fix must be performed client-side (i.e. on the machine running `astro deploy`).

If you experience this error, run `docker logout` for each Astro registry that this machine has cached credentials for. By default, credentials are stored in ~/.docker/config.json, and if you are using this default setting, the following bash script will identify cached credentials and run docker logout for those that correspond to Astro registries.

for domain in $(grep 'registry.astronomer.run' ~/.docker/config.json | awk '{print $1}' | tr -d '":' | sort | uniq); do
docker logout "$domain"
done
May 20, 17:25 UTC
Monitoring - We've implemented a mitigation for this issue and the affected clusters should see successful image pushes. We will continue to monitor for additional errors.
May 20, 16:52 UTC
Investigating - A small subset of customers have reported 403 errors when running the astro deploy command to deploy a new image. We are actively investigating this issue. If you are experiencing these errors, we encourage you to contact support and include the login command you used, astro cli and docker versions, and any log messages.
May 20, 16:02 UTC
May 19, 2025

No incidents reported.

May 18, 2025

No incidents reported.

May 17, 2025

No incidents reported.

May 16, 2025
Identified a configuration issue affecting Runtime 9 which is affecting DAG execution on these deployments
Resolved - This incident has been resolved.
May 16, 13:09 UTC
Identified - Fix has been validated and is rolling out to affected deployments.
May 16, 12:12 UTC
Investigating - We are currently investigating the issue.
May 16, 11:28 UTC
May 15, 2025

No incidents reported.

May 14, 2025

No incidents reported.

May 13, 2025

No incidents reported.

May 12, 2025

No incidents reported.

May 11, 2025

No incidents reported.

May 10, 2025

No incidents reported.

May 9, 2025

No incidents reported.

May 8, 2025

No incidents reported.

May 7, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage