Is Rudderstack down?

Last checked 11m ago
Current status
Rudderstack is up

No incidents right now.

Official status page: https://status.rudderstack.com · Polled every 5 minutes · 12 components tracked

Rudderstack is operational right now. Last checked 11m ago; the most recent incident resolved 11d ago.

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

Users who monitor Rudderstack also follow these CRM services: HubSpot Intercom Jira Service Desk ActiveCampaign Teamwork Alchemer Formstack Help Scout Intapp Bullhorn View all 6,000+ providers
Rudderstack uptime 99.58% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 17m
    Started May 08, 2026, 03:44 AM UTC · Resolved May 08, 2026, 04:02 AM UTC
    Data Ingestion (US)
    Timeline · 3 updates
    • investigating · May 08, 2026, 03:44 AM UTC

      We are currently investigating the issue. Enterprise customers are NOT affected by this issue.

    • investigating · May 08, 2026, 03:45 AM UTC

      AWS is having a major issue with load balancers which is also affecting our ingestion layer. We are working to fix the issue.

    • resolved · May 08, 2026, 04:02 AM UTC

      This incident has been resolved

    Latest: This incident has been resolved

  2. Resolved 15m
    Started May 08, 2026, 02:47 AM UTC · Resolved May 08, 2026, 03:02 AM UTC
    Data Ingestion (US)
    Timeline · 5 updates
    • investigating · May 08, 2026, 02:47 AM UTC

      We are currently investigating the issue. Enterprise customers are NOT affected by this issue.

    • investigating · May 08, 2026, 02:49 AM UTC

      AWS is having a major issue with load balancers which is also affecting our ingestion layer. We are working to fix the issue.

    • monitoring · May 08, 2026, 02:55 AM UTC

      We are seeing improvement on event ingestion metrics, currently monitoring.

    • monitoring · May 08, 2026, 02:58 AM UTC

      We are seeing significant improvement in event ingestion, the team is still monitoring.

    • resolved · May 08, 2026, 03:02 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 2h 23m
    Started May 08, 2026, 12:33 AM UTC · Resolved May 08, 2026, 02:57 AM UTC
    Data Processing Pipeline (US)Warehouses
    Timeline · 9 updates
    • investigating · May 08, 2026, 12:33 AM UTC

      We are currently investigating an issue on our data processing pipeline due to an EC2 instance availability issue in the US region.

    • investigating · May 08, 2026, 12:43 AM UTC

      We are investigating instance impairments in a single Availability Zone (use1-az4) in the US-EAST-1 Region.

    • investigating · May 08, 2026, 01:04 AM UTC

      We are still investigating the issue.

    • investigating · May 08, 2026, 01:31 AM UTC

      We are moving some workloads away from the problematic availability zone in AWS.

    • identified · May 08, 2026, 01:51 AM UTC

      We are actively working on a solution to the issue.

    • identified · May 08, 2026, 01:57 AM UTC

      We are continuing to work on a fix for this issue.

    • identified · May 08, 2026, 02:12 AM UTC

      Enterprise customers are not affected by this issue. The team is working on the issue for Free, Starter and Growth customers.

    • monitoring · May 08, 2026, 02:32 AM UTC

      Event processing has been resumed for Free, Starter and Growth customers, we are monitoring the pipeline's health.

    • resolved · May 08, 2026, 02:57 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved
    Started Apr 13, 2026, 06:31 AM UTC · Resolved Apr 13, 2026, 06:31 AM UTC
    Timeline · 1 update
    • resolved · Apr 13, 2026, 07:09 AM UTC

      Ingestion was impacted for customers on the Starter and Growth tiers from 06:31 AM to 06:50 AM UTC. The issue was caused by changes in a request routing service, which resulted in dropped traffic. The issue has been identified and resolved.

    Latest: Ingestion was impacted for customers on the Starter and Growth tiers from 06:31 AM to 06:50 AM UTC. The issue was caused by changes in a request routing service, which resulted in …

  5. Resolved
    Started Apr 08, 2026, 01:55 PM UTC · Resolved Apr 08, 2026, 01:55 PM UTC
    Timeline · 1 update
    • resolved · Apr 10, 2026, 04:26 PM UTC

      Summary: We experienced an issue affecting the Facebook Custom destination where events were not delivered due to a bug. Event delivery was paused during the window listed above. Impact: All active connections are rETL connections. Most connections have the "retry failed records" setting enabled — these will automatically deliver missed events during the next scheduled sync. However, connections without retry enabled will require the customer to perform a full sync. Resolution: The underlying bug has been fixed, and normal event delivery has resumed as of 10 Apr 2026 14:53 GMT.

    Latest: Summary: We experienced an issue affecting the Facebook Custom destination where events were not delivered due to a bug. Event delivery was paused during the window listed above. I…

See the full Rudderstack outage history

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

Browse Rudderstack outage history →

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

Outage history

Past 90 days · 7 incidents View full outage history →