Is Astronomer down?

Last checked 6m ago
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 6m ago; the most recent incident resolved 5h 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 15 incidents in the last 90 days (98.85% 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 98.85% uptime · past 90 days
Mon Wed Fri
MayJunJul
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 6h 35m
    Started Jul 30, 2026, 04:02 PM UTC · Resolved Jul 30, 2026, 10:38 PM UTC
    Timeline · 8 updates
    • investigating · Jul 30, 2026, 04:02 PM UTC

      We are currently investigating an issue with platform log ingestion for Astro. Logs may not be available in the Cloud UI.

    • investigating · Jul 30, 2026, 04:33 PM UTC

      We are continuing to investigate this issue, and will provide another update in 30mins or as new information is available.

    • identified · Jul 30, 2026, 06:03 PM UTC

      We have identified the source of increased log generation volume, which is causing issues on the ingestion side. We're implementing mitigations now and are monitoring the results.

    • identified · Jul 30, 2026, 06:43 PM UTC

      We are continuing to investigate and monitor this issue.

    • monitoring · Jul 30, 2026, 07:06 PM UTC

      We are beginning to see ingestion catch up with backlog log load. Customers may begin to see some logs becoming available in the Cloud UI

    • monitoring · Jul 30, 2026, 08:05 PM UTC

      We continue to see log ingestion improving on the platform, and we're continuing to monitor the situation.

    • monitoring · Jul 30, 2026, 09:47 PM UTC

      We are continuing to see progress as the log injestions works through the backlog. Available logs are now about ~20mins old, and we expect to see that latency return to normal baseline in the next 2 hours.

    • resolved · Jul 30, 2026, 10:38 PM UTC

      Ingestion lag is back at baseline

    Latest: Ingestion lag is back at baseline

  2. Resolved 28m
    Started Jul 07, 2026, 10:18 PM UTC · Resolved Jul 07, 2026, 10:47 PM UTC
    Timeline · 3 updates
    • investigating · Jul 07, 2026, 10:18 PM UTC

      We have detected node scaling issues in the Azure EastUS2 region and are currently investigating.

    • monitoring · Jul 07, 2026, 10:46 PM UTC

      Engineers observe that affected clusters are returning to "healthy" status.

    • resolved · Jul 07, 2026, 10:47 PM UTC

      The incident is fully resolved and all Azure clusters in EastUS2 are functioning as expected.

    Latest: The incident is fully resolved and all Azure clusters in EastUS2 are functioning as expected.

  3. Resolved 4h 30m
    Started Jul 06, 2026, 11:35 AM UTC · Resolved Jul 06, 2026, 04:06 PM UTC
    Timeline · 5 updates
    • investigating · Jul 06, 2026, 11:35 AM UTC

      We are investigating a spike in issues in AWS us-east-1 region, affecting node scale-up. This will create issues with workers scaling up and potentially new tasks starting

    • investigating · Jul 06, 2026, 01:00 PM UTC

      AWS has published a status update for this issue. We are actively monitoring their progress and will continue to share updates.

    • monitoring · Jul 06, 2026, 02:24 PM UTC

      AWS has now acknowledged a us-east-1 EC2 Launch Template API incident impacting EKS node provisioning/scaling (incl. Karpenter). We are continuing to monitor the situation.

    • monitoring · Jul 06, 2026, 03:00 PM UTC

      We are no longer seeing any impacting clusters in the AWS us-east-1 region. We're continuing to monitor the situation.

    • resolved · Jul 06, 2026, 04:06 PM UTC

      AWS has confirmed this incident is resolved.

    Latest: AWS has confirmed this incident is resolved.

  4. Resolved 47m
    Started Jun 16, 2026, 12:05 AM UTC · Resolved Jun 16, 2026, 12:53 AM UTC
    Timeline · 4 updates
    • identified · Jun 16, 2026, 12:05 AM UTC

      **The issue, according to Azure status page** Investigating a spike in 401 authentication errors We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We've identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly. This message was last updated at 23:04 UTC on 15 June 2026

    • monitoring · Jun 16, 2026, 12:05 AM UTC

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

    • investigating · Jun 16, 2026, 12:05 AM UTC

      We are currently investigating this issue.

    • resolved · Jun 16, 2026, 01:07 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Resolved 1h 25m
    Started Jun 15, 2026, 11:27 PM UTC · Resolved Jun 16, 2026, 12:53 AM UTC
    Scheduling and Running DAGs and TasksScheduling and Running DAGs and Tasks
    Timeline · 4 updates
    • investigating · Jun 15, 2026, 11:27 PM UTC

      We are currently investigating this issue.

    • identified · Jun 15, 2026, 11:28 PM UTC

      The issue, according to Azure status page ---- Investigating a spike in 401 authentication errors We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We've identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly. This message was last updated at 23:04 UTC on 15 June 2026

    • monitoring · Jun 15, 2026, 11:34 PM UTC

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

    • resolved · Jun 16, 2026, 12:53 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Astronomer outage history

10 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 · 15 incidents View full outage history →