Rudderstack Outage History
Rudderstack is up right nowPingoru has recorded 50 incidents for Rudderstack: 27 in the last 12 months and 3 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 0 of 720 (0%) |
| May 2026 | 3 | 3 of 744 (0%) |
| June 2026 | 2 | 2 of 720 (0%) |
| July 2026 | 6 | 14 of 744 (2%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 2 | 2 of 720 (0%) |
| October 2026 | 0 | 0 of 511 (0%) |
Incidents, newest first
Major October 20, 2025 Issues with python transformations in US. 6h 18m Data Processing Pipeline (US)
Started Oct 20, 2025, 03:32 PM UTC· resolved Oct 20, 2025, 09:51 PM UTC
- identified Oct 20, 2025, 03:32 PM UTC
RudderStack is actively working to resolve the issues caused by the ongoing AWS incident. Currently, customers in US using Python Transformations are impacted, and we are focused on restoring this feature as soon as possible. Our efforts are currently constrained by limited AWS resource availability, but we are exploring multiple options to restore full functionality. We will share another update as soon as we have more information.
- monitoring Oct 20, 2025, 07:06 PM UTC
We are seeing successful increased launches of new EC2 instances and thus able to resource python transformations. We will be monitoring till all the backlog is cleared
- resolved Oct 20, 2025, 09:51 PM UTC
RudderStack has cleared all backlog across all the python transformations. We do not see any lingering impact to customers. If you have questions contact your account team
Minor October 20, 2025 Destination deliveries delays 10h 34m Data Processing Pipeline (US), Web Application
Started Oct 20, 2025, 11:16 AM UTC· resolved Oct 20, 2025, 09:50 PM UTC
- identified Oct 20, 2025, 11:16 AM UTC
Due to an ongoing AWS incident, a small portion of US customers are experiencing significant delivery latencies of more than an hour. However, event ingestion remains unaffected and no data loss has occurred. We are actively looking at ways to mitigate the issue. https://health.aws.amazon.com/health/status
- identified Oct 20, 2025, 12:39 PM UTC
Customer-facing monitoring dashboards are also affected and may be incorrect, but this is a display issue only—data continues to be ingested normally and no data loss has occurred.
- identified Oct 20, 2025, 02:17 PM UTC
Data processing and event delivery has returned for most customers, a small subset of customers are still seeing impact due to AWS limiting resources. Our team is working to inform this small set of customers while working to restore the service. Data ingestion remains for these customers, processing and delivery remain impacted.
- identified Oct 20, 2025, 05:04 PM UTC
Data processing and event delivery has returned for all production customer workspaces although it might be delayed for some end destinations if those themselves are impacted by the AWS incident
- monitoring Oct 20, 2025, 05:06 PM UTC
Data processing and event delivery has returned for all production customer workspaces although it might be delayed for some end destinations if those themselves are impacted by the AWS incident
- resolved Oct 20, 2025, 09:50 PM UTC
RudderStack has cleared all backlog across all customers. We do not see any lingering impact to customers. If you have questions contact your account team
Minor October 20, 2025 AWS Cloud Provider Outage –
Started Oct 20, 2025, 07:30 AM UTC· resolved Oct 20, 2025, 07:30 AM UTC
- resolved Oct 20, 2025, 10:18 AM UTC
We experienced an issue with our AWS cloud provider, which caused temporary disruptions to web app login functionality. https://health.aws.amazon.com/health/status Users may have been unable to log in during this period. Ingestion services were not impacted, all data continued to flow and process as expected.
Notice August 21, 2025 Partial delivery failures to TikTok destinations 8h 30m Data Processing Pipeline (US), Data Processing Pipeline (EU)
Started Aug 21, 2025, 07:00 AM UTC· resolved Aug 21, 2025, 03:30 PM UTC
- investigating Aug 22, 2025, 01:41 PM UTC
We are currently investigating the issue around failures for TikTok destinations
- identified Aug 22, 2025, 01:42 PM UTC
The issue has been identified and rollback is in progress
- resolved Aug 22, 2025, 01:44 PM UTC
The incident has been resolved. Changes made to determine how event_source is set to TikTok events broke the deliveries for its server SDK sources. Change has been reverted and failures have been replayed for all customers with configured backup
Notice August 14, 2025 Delivery failures to salesforce destinations 23h 23m Data Processing Pipeline (US), Data Processing Pipeline (EU)
Started Aug 14, 2025, 08:08 PM UTC· resolved Aug 15, 2025, 07:32 PM UTC
- investigating Aug 18, 2025, 03:29 PM UTC
We are currently investigating the issue around failures for salesforce destinations
- identified Aug 18, 2025, 03:30 PM UTC
The issue has been identified and remediation is being implemented
- resolved Aug 18, 2025, 03:32 PM UTC
The incident has been resolved. Recently, Salesforce decided to enforce client_id validation and rolled out changes that made this field mandatory. Fix has been made pass the client_id. Failures have been replayed for all customers with salesforce destinations. Pipelines with rETL sources to salesforce will be processed in the next scheduled sync
Notice July 2, 2025 We're investigating reports of an issue with Google Ads API's. 11h Data Processing Pipeline (US)
Started Jul 02, 2025, 04:30 PM UTC· resolved Jul 03, 2025, 03:30 AM UTC
- investigating Jul 03, 2025, 03:16 PM UTC
We are currently investigating this issue.
- resolved Jul 03, 2025, 03:18 PM UTC
Deliveries to Google Ads Offline Conversions were impacted due to issues (unavailable, high latency and unexpected behavior) with Google Ads API as reported by Google (https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu). We’ve identified the affected customers and have completed a replay for all impacted destinations.
Notice June 12, 2025 Cloudflare and GCP outage causing delayed deliveries to affected cloud destinations 2h Data Processing Pipeline (US), Data Processing Pipeline (EU)
Started Jun 12, 2025, 08:27 PM UTC· resolved Jun 12, 2025, 10:27 PM UTC
- monitoring Jun 12, 2025, 08:27 PM UTC
Cloudflare and GCP have reported recovery and we are actively monitoring to ensure all events are retried and delivered to affected destinations. No data loss has been observed
- resolved Jun 12, 2025, 10:27 PM UTC
This incident has been resolved.
Minor May 28, 2025 Incorrect Delivery for S3 and S3 Datalake 2h 15m Data Processing Pipeline (US), Warehouses
Started May 28, 2025, 05:00 PM UTC· resolved May 28, 2025, 07:15 PM UTC
- identified May 29, 2025, 01:40 PM UTC
Issue has been identified with S3 and S3 datalake deliveries. Actively working on the fix.
- resolved May 29, 2025, 01:40 PM UTC
An issue was identified with the delivery module for S3 & S3_DATALAKE destinations, leading to the incorrect duplication of the prefix in the final file path. This resulted in data being uploaded to an unintended location, making it unavailable for any downstream consumption for the duration of the incident. The flag was enabled only for free tier and starter and growth customers. Follow the below recommended steps to recover the data: Prerequisite: Make sure the AWS CLI is installed and configured locally to access the relevant S3 bucket. 1. Go to the Rudderstack configuration page of your S3/S3 Datalake destinations and copy bucket name and prefix. 2. Copy all the files from the double-prefix path to the single prefix path. Command: aws s3 cp s3://{bucket_name}/{prefix}/{prefix}/ s3://{bucket_name}/{prefix}/ --recursive 3. Delete the original files (optional) Command:aws s3 rm s3://{bucket_name}/{prefix}/{prefix}/ --recursive
Notice May 11, 2025 Ingestion failures for webhook sources 50m Data Ingestion (US), Data Ingestion (EU)
Started May 11, 2025, 06:10 PM UTC· resolved May 11, 2025, 07:00 PM UTC
- investigating May 11, 2025, 06:57 PM UTC
We are currently investigating this issue.
- identified May 11, 2025, 06:58 PM UTC
The issue has been identified and a fix is being implemented. Unrelated configuration changes caused the autoscaling system to misbehave, which resulted in timeouts with one of our services
- monitoring May 11, 2025, 06:59 PM UTC
We reverted the configuration changes responsible for the issue and we are monitoring the results.
- resolved May 11, 2025, 07:00 PM UTC
This incident has been resolved and no further ingestion failures are being observed
Major March 3, 2025 Data loss of small percentage of warehouse events on free tier 1h Warehouses
Started Mar 03, 2025, 09:00 AM UTC· resolved Mar 03, 2025, 10:00 AM UTC
- investigating Mar 06, 2025, 09:48 PM UTC
We are currently investigating this issue.
- identified Mar 06, 2025, 09:48 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Mar 06, 2025, 09:48 PM UTC
This incident has been resolved. During the migration of our internal database, certain custom configurations from the previous version were not restored in the new setup. This led to degraded service performance, causing failing health checks and an increase in service restarts.
Minor February 18, 2025 Partial outage for some sources 35m
Started Feb 18, 2025, 08:55 AM UTC· resolved Feb 18, 2025, 09:30 AM UTC
- 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
Major February 5, 2025 Google Ads offline conversion destination got impacted. –
Started Feb 05, 2025, 01:00 PM UTC· resolved Feb 05, 2025, 01:00 PM UTC
- 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.
Major December 27, 2024 High rate of 5xx in ingestion of events for starter and growth tier in US region 19m Data Ingestion (US)
Started Dec 27, 2024, 10:55 PM UTC· resolved Dec 27, 2024, 11:15 PM UTC
- investigating Jan 07, 2025, 03:50 PM UTC
We are actively investigating the issue
- resolved Jan 07, 2025, 03:52 PM UTC
Ingestion is back to normal and this incident is resolved
Major December 17, 2024 Incorrect MIME Type Headers for JavaScript SDK Plugin Artifacts –
Started Dec 17, 2024, 09:45 AM UTC· resolved Dec 17, 2024, 09:45 AM UTC
- 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.
Major October 22, 2024 Ingestion got affected for customers on pro tier in EU region. 15m
Started Oct 22, 2024, 10:00 AM UTC· resolved Oct 22, 2024, 10:15 AM UTC
- 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.