- 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 1h 54m it lasted.
Anything that failed between 2026-07-06 11:49 UTC and 2026-07-06 13:43 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 4
- identified
We have identified an issue with our cloud service provider, which prevents us to preemptly scaling our infrastructure. Data ingestion has not been affected. We expect a delay in event delivery for some customers in the US region.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
We are observing an improvement in API calls to our cloud service provider.
provider
- resolved
This incident has been resolved.
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-eb52a1d316
Is RudderStack still down?
No, this incident was resolved 2026-07-06 13:43 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
1h 54m, from 2026-07-06 11:49 UTC to 2026-07-06 13:43 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.