Skip to main content
RudderStack

Destination deliveries delays

Degraded Lasted 10h 34m · started · RudderStack's page

Level
confirmed
Worst impact
Degraded
Components
Data Processing Pipeline (US), Web Application
Regions
us
Down Index
27of 100

What to do

  • Check whether you use RudderStack Data Processing Pipeline (US), Web Application in us. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 10h 34m it lasted.

    Anything that failed between 2025-10-20 11:16 UTC and 2025-10-20 21:50 UTC may need a replay.
  • Subscribe to RudderStack's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=rudderstack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from RudderStack 6

  1. identified

    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

    provider

  2. identified

    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.

    provider

  3. identified

    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.

    provider

  4. identified

    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

    provider

  5. monitoring

    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

    provider

  6. resolved

    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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-92c18716bf

Is RudderStack still down?

No, this incident was resolved 2025-10-20 21:50 UTC. For RudderStack's live state, see https://down.guide/rudderstack.

How long did it last?

10h 34m, from 2025-10-20 11:16 UTC to 2025-10-20 21:50 UTC, by the times RudderStack posted.

What was affected?

RudderStack named Data Processing Pipeline (US), Web Application in us.

What caused it?

RudderStack hasn't published a root cause. If it does, it shows here.

Where does this come from?

RudderStack's official status page, https://status.rudderstack.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.