Rudderstack Outage History

Rudderstack is up right now

Rudderstack had 34 outages in the last 2 years totaling 3h 54m of downtime — averaging 1.4 incidents per month.

There were 34 Rudderstack outages since July 15, 2024 totaling 3h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.rudderstack.com

Minor February 18, 2025

Partial outage for some sources

Detected by Pingoru
Feb 18, 2025, 09:00 AM UTC
Resolved
Feb 18, 2025, 09:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 18, 2025, 12:42 PM UTC

    On 18th Feb, We experienced a partial outage affecting some sources: Webhook, Customer.io, AppsFlyer, Shopify, Braze, Auth0, Iterable, Monday, Adjust, Pipedream, and Segment. This issue impacted some Enterprise US customers, leading to failure to ingest data. Our team identified and resolved the issue, all affected services are fully operational. Data is now flowing as expected. Start Time: 08:55 UTC End Time: 09:30 UTC

Read the full incident report →

Major February 5, 2025

Google Ads offline conversion destination got impacted.

Detected by Pingoru
Feb 05, 2025, 01:00 PM UTC
Resolved
Feb 05, 2025, 01:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 06, 2025, 12:32 PM UTC

    On 5th feb, Events began failing for Google Ads offline conversion destinations due to the deprecation of Google Ads API v16 in both the US and EU regions. As a result, affected customers may have experienced missing or delayed data. We performed an event replay for impacted destinations to recover lost data. Customers who did not have a backup in place may still experience data loss. The incident is now fully resolved. If you continue to see any related issues or have any concerns, please contact our support team for further assistance.

Read the full incident report →

Major December 17, 2024

Incorrect MIME Type Headers for JavaScript SDK Plugin Artifacts

Detected by Pingoru
Dec 17, 2024, 09:45 AM UTC
Resolved
Dec 17, 2024, 09:45 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 17, 2024, 04:07 PM UTC

    Incident Summary: RudderStack encountered an issue where JavaScript SDK plugin artifacts were served with incorrect MIME type headers (binary/octet-stream) from our CDN. This caused modern browsers to reject the scripts, resulting in plugin loading failures and a loss of instrumented events to RudderStack and device mode destinations. Impact: The issue did not affect all customers uniformly due to the nature of content distribution via the CDN. Some customers experienced the issue earlier as their regions picked up the changes, while others saw delayed or minimal impact. Resolution: The incorrect MIME type was promptly corrected to application/javascript, and normal functionality was restored. We sincerely apologize for any inconvenience caused and thank you for your understanding. If you have further questions or concerns, please contact our support team.

Read the full incident report →

Major October 22, 2024

Ingestion got affected for customers on pro tier in EU region.

Detected by Pingoru
Oct 22, 2024, 10:46 AM UTC
Resolved
Oct 22, 2024, 10:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 22, 2024, 10:46 AM UTC

    Customers in EU region on pro tier ingestion got affected from 10:00AM to 10:15AM UTC. For JS and mobile SDKs, events would have got retried and server-side SDKs, there is a possibility of data loss. This is resolved now.

Read the full incident report →

Critical September 25, 2024

Ingestion got affected for customers in US enterprise tier

Detected by Pingoru
Sep 25, 2024, 09:37 AM UTC
Resolved
Sep 25, 2024, 11:09 AM UTC
Duration
1h 31m
Affected: Data Ingestion (US)
Timeline · 4 updates
  1. investigating Sep 25, 2024, 09:37 AM UTC

    We are currently investigating the issue

  2. identified Sep 25, 2024, 09:46 AM UTC

    The issue has been identified and fix is being implemented.

  3. monitoring Sep 25, 2024, 10:02 AM UTC

    A fix has been implemented few minutes back and systems got recovered. We are currently monitoring the same and customers can expect the ingestion back to normal.

  4. resolved Sep 25, 2024, 11:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Major September 5, 2024

Ingestion failure for a subset of webhook source events

Detected by Pingoru
Sep 05, 2024, 03:00 PM UTC
Resolved
Sep 05, 2024, 03:30 PM UTC
Duration
30m
Affected: Data Ingestion (US)Data Ingestion (EU)
Timeline · 3 updates
  1. investigating Sep 06, 2024, 06:09 PM UTC

    We are actively investigating this issue

  2. identified Sep 06, 2024, 06:10 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Sep 06, 2024, 06:13 PM UTC

    This incident has been resolved

Read the full incident report →

Notice July 25, 2024

Ingestion affected for starter and growth customers in EU region

Detected by Pingoru
Jul 25, 2024, 04:27 AM UTC
Resolved
Jul 25, 2024, 04:28 AM UTC
Duration
1m
Affected: Data Ingestion (EU)
Timeline · 3 updates
  1. investigating Jul 25, 2024, 04:27 AM UTC

    We are currently investigating this issue.

  2. identified Jul 25, 2024, 04:28 AM UTC

    The issue has been identified and a fix is being rolled out

  3. resolved Jul 25, 2024, 04:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 15, 2024

Intercom destination got affected for all customer tiers.

Detected by Pingoru
Jul 15, 2024, 12:23 PM UTC
Resolved
Jul 15, 2024, 01:54 PM UTC
Duration
1h 31m
Affected: Data Processing Pipeline (US)Data Processing Pipeline (EU)
Timeline · 3 updates
  1. identified Jul 15, 2024, 12:23 PM UTC

    We have identified that a Web Application Firewall (WAF) from Intercom's side is blocking requests when the User-Agent header is set to RudderLabs. Our team is actively working to resolve this issue as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience.

  2. monitoring Jul 15, 2024, 01:11 PM UTC

    The issue has been fixed, and we are currently monitoring it.

  3. resolved Jul 15, 2024, 01:54 PM UTC

    This incident has been resolved. Incident timeline: 13th July, 11:15 PM (UTC) to 15th July, 11:10 AM (UTC)

Read the full incident report →