- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing Pipeline (US)
- Regions
- us
What to do
Check whether you use RudderStack Data Processing Pipeline (US) 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 2h 13m it lasted.
Anything that failed between 2026-03-19 15:11 UTC and 2026-03-19 17:23 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 2
- identified
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
provider
- resolved
Incident has been resolved and the pipeline processing and delivery is back to realtime
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-094e36816e
Is RudderStack still down?
No, this incident was resolved 2026-03-19 17:23 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
2h 13m, from 2026-03-19 15:11 UTC to 2026-03-19 17:23 UTC, by the times RudderStack posted.
What was affected?
RudderStack named Data Processing Pipeline (US) 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.