Is Astronomer down?

Last checked just now
Current status
Astronomer is up

No incidents right now.

Official status page: https://status.astronomer.io · Polled every 5 minutes · 15 components tracked

Astronomer is operational right now. Last checked just now; the most recent incident resolved 36d ago.

Real-time Astronomer status, recent outages, and incident history — pulled directly from Astronomer's official status page at https://status.astronomer.io every 5 minutes. Pingoru tracks 15 Astronomer services and has captured 11 incidents in the last 90 days (97.48% uptime). Get email, Slack, Discord, or webhook alerts the moment Astronomer reports a new incident — free for 5 monitors, no credit card.

Users who monitor Astronomer also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Astronomer uptime 97.48% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 18h
    Started May 08, 2026, 07:43 AM UTC · Resolved May 09, 2026, 01:43 AM UTC
    Scheduling and Running DAGs and TasksScheduling and Running DAGs and Tasks
    Timeline · 3 updates
    • investigating · May 08, 2026, 07:43 AM UTC

      We are currently observing elevated task failures and latency for some deployments running in the AWS us-east-1 region. This is related to an ongoing AWS incident affecting a single Availability Zone (use1-az4), where EC2 and EBS resources have experienced impairments. What to expect: You may see intermittent task failures or retries in your deployments. In most cases, these failures are transient and should self-resolve automatically as AWS continues recovery. What you should do: No immediate action is required. However, if you notice consistent or prolonged failures, please reach out to Astronomer Support, and we’ll help investigate further. We are continuing to monitor the situation closely and will share updates as needed. Refer: https://health.aws.amazon.com/health/status

    • monitoring · May 08, 2026, 07:45 AM UTC

      We are continuing to monitor the situation as AWS works toward full recovery in the affected Availability Zone. At this time, we are seeing signs of stabilization, and most transient failures should continue to self-resolve. We will provide further updates once AWS confirms that the issue has been fully resolved.

    • resolved · May 09, 2026, 01:43 AM UTC

      AWS 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. Any previously impacted workloads should now be operating as expected. If you continue to experience issues, please reach out to Astronomer Support for assistance.

    Latest: AWS 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 …

  2. Resolved 3h 53m
    Started May 07, 2026, 10:31 AM UTC · Resolved May 07, 2026, 02:24 PM UTC
    Astro Observe
    Timeline · 5 updates
    • investigating · May 07, 2026, 10:31 AM UTC

      We are investigating delayed delivery for some time-based alerts. The delay is primarily visible for DAG Timeliness alerts, and may also affect Observe-related SLA, Proactive SLA, and Data Quality monitor alerts. DAG Duration and Task Duration alerts do not appear to be affected at this time.

    • identified · May 07, 2026, 11:15 AM UTC

      We have identified the cause of the delayed delivery for some time-based alerts and are implementing a fix. We will provide another update once the fix has been deployed and validated.

    • identified · May 07, 2026, 12:57 PM UTC

      A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway.

    • monitoring · May 07, 2026, 01:49 PM UTC

      A fix has been implemented, and we are monitoring the results.

    • resolved · May 07, 2026, 02:24 PM UTC

      The incident has been resolved.

    Latest: The incident has been resolved.

  3. Resolved 9m
    Started May 06, 2026, 07:56 PM UTC · Resolved May 06, 2026, 08:05 PM UTC
    Deployment Access
    Timeline · 2 updates
    • investigating · May 06, 2026, 07:56 PM UTC

      Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.

    • resolved · May 06, 2026, 08:05 PM UTC

      Our team has determined this only affects internal access, Astro end users are unaffected.

    Latest: Our team has determined this only affects internal access, Astro end users are unaffected.

  4. Resolved 9h 18m
    Started May 04, 2026, 10:56 AM UTC · Resolved May 04, 2026, 08:15 PM UTC
    Dashboards and Analytics
    Timeline · 3 updates
    • investigating · May 04, 2026, 10:56 AM UTC

      We’re investigating an issue affecting Dashboard cost breakdown data. For affected customers, cost breakdown information may appear stale and may not have updated since May 1, 2026. Our team is actively investigating the cause and working to restore current data. We’ll share another update as we have more information.

    • investigating · May 04, 2026, 10:56 AM UTC

      We are continuing to investigate this issue.

    • resolved · May 04, 2026, 08:15 PM UTC

      This 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.

    Latest: This 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.

  5. Resolved 2h 11m
    Started Apr 27, 2026, 10:04 PM UTC · Resolved Apr 28, 2026, 12:16 AM UTC
    Deployment AccessDeployment Management
    Timeline · 3 updates
    • investigating · Apr 27, 2026, 10:04 PM UTC

      It seems to be only in AWS clusters for now. We have a workaround while we investigate.

    • investigating · Apr 27, 2026, 10:05 PM UTC

      We are continuing to investigate this issue.

    • resolved · Apr 28, 2026, 12:16 AM UTC

      We 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 their 403s resolved themselves after some time.

    Latest: We 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 itsel…

See the full Astronomer outage history

6 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Astronomer outage history →

Or sign up free to get alerts when Astronomer breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 11 incidents View full outage history →