Rudderstack incident

Destination deliveries delays

Minor Resolved View vendor source →

Rudderstack experienced a minor incident on October 20, 2025 affecting Data Processing Pipeline (US) and Web Application, lasting 10h 34m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 11:16 AM UTC
Resolved
Oct 20, 2025, 09:50 PM UTC
Duration
10h 34m
Detected by Pingoru
Oct 20, 2025, 11:16 AM UTC

Affected components

Data Processing Pipeline (US)Web Application

Update timeline

  1. 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

  2. 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.

  3. 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.

  4. 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

  5. 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

  6. 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