Astro Outage History

41 incidents recorded over the last 365 days, 39 of them resolved, 1 still open. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Astro Incident

Astro incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 7, 2026Scheduled Astro Web and API Maintenance — November 7**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…3h 0mScheduled
Oct 22, 2026PHP Security Advisory: Astro and Astro Private Cloud Not Affected; Review Custom Images**PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619) ** Astronomer has conducted a thorough internal review of its code and container images and confirmed that Astro and Astro Private Cloud do not include PHP and…—Investigating
Oct 22, 2026Security Update: Runtime Releases and Guidance for the eMudhra/emSign Certificate IssueWe 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…45h 27mResolved
Oct 20, 2026Delayed delivery of Astro AlertsAstro 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.26h 9mResolved
Oct 19, 2026Organization Dashboards are failing to load with Invalid kid parameter errorThe issue has been resolved, and the Organization Dashboards are now working as expected.1h 23mResolved
Oct 13, 2026Astro UI and API are appearing offline for some usersWe 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.1h 51mResolved
Oct 6, 2026Capacity constraints in GCP us-central1 may delay or fail some task executionsWe 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…189h 0mResolved
Oct 3, 2026Dag success/failure Astro Alert emails missing deployment & workspace namesAll Astro Alert emails for Dag Success/Failure now correctly include the deployment/workspace name.56 minResolved
Oct 1, 2026Tasks getting stuck in the queued state and failingOur development team has concluded that this was a false alert. It is not affecting multiple deployments.1h 7mResolved
Sep 24, 2026Astro UI Deployment view unavailableIssue 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.41 minResolved
Sep 17, 2026Permissions silently dropped from custom rolesNo further issues have been found, so this is being marked as resolved.3h 56mResolved
Sep 8, 2026Tasks remain in the queued state on some worker queues.The incident has been resolved.7h 35mResolved
Sep 4, 2026Increased auth errorsThe 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.2h 58mResolved
Sep 1, 2026Potential impact to Astro deployments in GCP us-central1The GCP incident is marked as Closed officially3h 49mResolved
Aug 18, 2026Incorrect scheduler heartbeat metrics being reportedThis issue is now resolved.555h 27mResolved
Aug 18, 2026Intermittent task instances failures.Rollout has been completed3h 18mResolved
Aug 4, 2026KPO podspec changes for GPU-enabled nodes may cause KPO pod startup failuresMitigations have been successful. A Platform release that corrects this errant behavior is being worked on now. Issue is resolved.1h 29mResolved
Aug 4, 2026Intermittent Delays Managing Airflow Deployments in Azure Central USThis interruption has been resolved.1h 38mResolved
Jul 30, 2026Platform Log ingestion issueIngestion lag is back at baseline6h 35mResolved
Jul 7, 2026Node Scaling Issue in Azure EastUS2 RegionThe incident is fully resolved and all Azure clusters in EastUS2 are functioning as expected.28 minResolved
Jul 6, 2026Node Scaling issues in AWS us-east-1 regionAWS has confirmed this incident is resolved.4h 30mResolved
Jun 16, 2026Azure clusters may experience issues with worker scale up and task pod schedulingThis incident has been resolved.47 minResolved
Jun 15, 2026astro deploys not reflecting on certain Astro clustersMitigation was effective and all affected clusters are healthy.1h 27mResolved
May 8, 2026Increased Task Failures in US-East-1 (AWS) - AWS IncidentAWS has confirmed recovery in the affected Availability Zone (use1-az4), and system performance has returned to normal levels. We are no longer observing elevated task failures or latency in the AWS us-east-1 region…17h 37mResolved
May 7, 2026Delayed delivery for some time-based alertsThe incident has been resolved.3h 16mResolved
May 6, 2026Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.Our team has determined this only affects internal access, Astro end users are unaffected.0 minResolved
May 4, 2026Dashboard cost breakdown data delaysThis incident is now resolved, and all Cost Breakdown data is now up to date. The issue that caused the delay has been fixed and should not recur.9h 6mResolved
Apr 27, 2026Airflow UI showing 403s for some customersWe rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found…2h 9mResolved
Apr 24, 2026Azure East US multiservice outage impacting Astro deployments in the regionAzure has confirmed the issue is resolved and services are back to normal. This incident is now closed. For more details, see the Azure incident history: https://azure.status.microsoft/en-us/status/history/11h 37mResolved
Apr 17, 2026Terminating Workers Accepting Tasks Causing Failures in Astro ExecutorThis issue has been resolved.3h 39mResolved
Apr 16, 2026Runtime 3.2-1 Yanked - Incompatible with Env ManagerAstronomer Runtime 3.2-2 has been released with the fix.4h 18mResolved
Apr 13, 2026Degraded service for some deployments in Azure West Europe**RESOLVED** – Azure West Europe Cluster Capacity Issue We have resolved a capacity issue affecting our Azure West Europe (westeurope) shared cluster that occurred between 1:34 PM and 3:09 PM PDT on April 13. During…4 minResolved
Apr 12, 2026Astro Alerts Degraded PerformanceThe issue has been resolved. Over the weekend, we observed a degradation in alert performance. With the fix now applied, any missed alerts are expected to be delivered now, and new alerts will be triggered without…12h 15mResolved
Apr 2, 2026Astronomer Cloud OutageThis incident has been resolved.-2258345 minResolved
Apr 2, 2026AWS OutageThis incident has been resolved.-2259383 minResolved
Apr 2, 2026Image Registry UnavailableA fix is applied where we added a new query in astro API that retrieves deployments and updated the docker registry auth proxy to use that query-2268771 minResolved
Apr 2, 2026AWS OutageThis incident has been resolved.-2270020 minResolved
Apr 2, 2026API Key / Access Token IssueThis incident has been resolved.-2216341 minResolved
Apr 2, 2026Deployments and Login InstabilityThis incident has been resolved.-2257844 minResolved
Apr 2, 2026New images not being deployedThis incident has been resolved.-2136513 minResolved
Apr 2, 2026Deployment Status is brokenThe incident has been resolved. All the deployments should be able to display correct Health status-2107876 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Astro incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Astro Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Astro acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Astro outage in this window ran 23d 3h, against a mean recovery of 1d 4h. If you depend on Astro in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.