Astronomer incident

Astro deployments in GCP us-central-1 experiencing issues

Major Resolved View vendor source →
Started
Mar 09, 2026, 01:29 PM UTC
Resolved
Mar 09, 2026, 04:11 PM UTC
Duration
2h 41m
Detected by Pingoru
Mar 09, 2026, 01:29 PM UTC

Affected components

Scheduling and Running DAGs and TasksScheduling and Running DAGs and TasksDeployment ManagementDeployment Management

Update timeline

  1. investigating Mar 09, 2026, 01:29 PM UTC

    Some pods in us-central-1 are experiencing CrashLoopBackoff errors. Because at least some of these errors are affecting the components that control Dag-only deploys, newly scaled up worker pods are being affected in at least some cases. We are actively investigating.

  2. investigating Mar 09, 2026, 01:53 PM UTC

    Google has confirmed to Astronomer that this is an issue with GKE in the region. We are following the issue closely.

  3. identified Mar 09, 2026, 03:30 PM UTC

    We are seeing signs of recovery across some affected clusters.

  4. resolved Mar 09, 2026, 04:11 PM UTC

    The GKE incident is now resolved per Google, and we are seeing that all related issues appear to have cleared up on Astro. If you are still experiencing an issue, please raise a support ticket.

Looking to track Astronomer downtime and outages?

Pingoru polls Astronomer's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Astronomer reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Astronomer alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Astronomer for free

5 free monitors · No credit card required