Rudderstack had 23 outages in the last 2 years totaling 486h 15m of downtime — averaging 0.9 incidents per month.
There were 23 Rudderstack outages since May 28, 2025 totaling 486h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating the issue. Enterprise customers are NOT affected by this issue.
AWS is having a major issue with load balancers which is also affecting our ingestion layer. We are working to fix the issue.
This incident has been resolved
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.
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.
During a scheduled maintenance activity on March 24, 2026, Public APIs and Activation APIs experienced a brief period of downtime across all regions between 00:10 – 00:40 UTC, during which requests returned HTTP 401 errors. The maintenance was completed and services recovered automatically. No data loss occurred and ingestion was unaffected. Public APIs — All Regions | Activation APIs — All Regions
Investigating: We are currently seeing delays in processing and delivery for Starter and Growth tier customers in the US region. Our team is investigating and will share updates as they become available. Note: Ingestion is unaffected and there is no observed data loss
Incident has been resolved and the pipeline processing and delivery is back to realtime
We’re seeing elevated errors and delayed event delivery to Facebook Marketing destinations. We’re actively monitoring and retrying failed requests; no action is required on your side at this time. Meta currently reports the Ads Creation and Editing API experiencing disruptions https://metastatus.com/marketing-api
This incident has been resolved.
The issue has been identified and a fix is being implemented.
Between 21:55 - 22:25 UTC RudderStack experienced a temporary ingestion issue which caused 5xx errors on ingestion for a subset of the EU customers. Based on the retry logic of the SDK, these events were likely retried but there might have been some data loss for Server Side SDK's during this timeframe. Also between 21:09 - 22:00 UTC we have observed timeout errors on some of the user transformation code executions that would have dropped the events. We will be running replay for such events wherever data retention is configured
Issue with backend service for a subset of customers has resulted in delay of the RETL syncs (activations) scheduled during this time window. Profiles UI would have failed to load for the customers too
We are currently investigating this issue.
We are investigating an issue causing an outage for a internal service, which is impacting several dependent components including the Control Plane and Activation API. Customers may experience errors accessing RudderStack web app or any other componets depending on it. Note: No impact on event ingestion on the data planes
We have identified the cause of the outage and rolling out a fix
We are seeing recovery of the services. We are continuing to monitor the system to ensure stability and confirm full restoration
This incident has been resolved and all services are back to normal
All events routed to the Mailchimp cloud-mode destination for starter and growth customers in US region are failing consistently.
We identified that RudderStack IPs are being blocked by Mailchimp’s Akamai proxy. We are working to establish an active communication channel with Mailchimp’s team to resolve this issue.
We resolved the issue for free tier customers. We are waiting on Mailchimp to establish an active communication channel to unblock our IPs for complete resolution.
We have identified and isolated events causing Mailchimp and Akamai flagging our public IP for some of our customers. Necessary steps have been taken and issue is resolved now for all customers including free tier users
This incident is impacting customers on our Growth, Starter, and Enterprise plans in the US region. Our team is actively investigating the issue. We’ll provide further updates as soon as we have more information. Start time: 15:17UTC
The issue was fully resolved at 15:32UTC, and we are no longer seeing any errors. Events related to mobile/web SDK will be retried. We are currently monitoring the system to ensure full stability.
The data ingestion issue impacting Enterprise, Growth, Starter and Pro tier customers in the US region has been fully resolved. The disruption was caused by an intermittent Cloudflare issue affecting a backend component. All systems are fully operational, and data ingestion is operating as expected.
This incident impacted Enterprise US customers and caused data ingestion failures. The issue has been fully resolved, all services are operational, and data is flowing as expected. Please reach out to Support if you have any questions. Issue Timeline: 14:37–14:52 UTC
The data ingestion issue impacting Enterprise customers in the US region has been fully resolved. The disruption was caused by an intermittent Cloudflare issue affecting a backend component. All systems are fully operational, and data ingestion is operating as expected.
We're aware of the ongoing Azure outage. At this time, RudderStack services are not impacted. Our team is actively monitoring the situation and prepared to take mitigation steps if the impact broadens.
This incident has been resolved.
Customers using the Databricks destination may be experiencing failed deliveries due to a recent change on Databricks’ side. Our team is actively working on a fix and will release an update shortly.
This incident has been resolved.
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.
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
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
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
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.
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.
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
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
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
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.
We are currently investigating the issue around failures for TikTok destinations
The issue has been identified and rollback is in progress
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
We are currently investigating the issue around failures for salesforce destinations
The issue has been identified and remediation is being implemented
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
We are currently investigating this issue.
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.
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
This incident has been resolved.
Issue has been identified with S3 and S3 datalake deliveries. Actively working on the fix.
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