- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing Pipeline (US), Data Processing Pipeline (EU)
- Regions
- eu, us
- Down Index
- 30of 100
What to do
Check whether you use RudderStack Data Processing Pipeline (US), Data Processing Pipeline (EU) in eu, 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 7h 12m it lasted.
Anything that failed between 2026-07-02 08:11 UTC and 2026-07-02 15: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 6
- investigating
We are investigating an increase in delivery failures (authentication errors) affecting a subset of Webhook destinations for some customers, beginning around 06:35 UTC on July 2. Event ingestion is not affected. We are actively investigating and will provide an update shortly.
provider
- identified
Elevated delivery failures for Webhook destinations We've identified the root cause of the delivery failures (authentication errors / HTTP 401) affecting some Webhook destinations. Event ingestion is unaffected — your data is being received and processed normally; only delivery to these destinations is impacted. Our engineering team is actively working on a fix and remediation is underway. We will post the next update as soon as recovery is confirmed. Immediate fix on your side: Open your Webhook destination settings in the dashboard, re-enter the keys/values in the Headers section (the previous values were reset), and save. Event delivery will resume right away.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We have developed a fix for the authentication errors affecting delivery to some Webhook destinations, and we are now actively deploying it across affected customers. The remediation restores the reset header values automatically, so impacted destinations will resume delivery as the rollout reaches them.
provider
- resolved
This incident has been resolved. If your workspace has Data Retention enabled, we are going to replay the events automatically.
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-cda465107c
Is RudderStack still down?
No, this incident was resolved 2026-07-02 15:23 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
7h 12m, from 2026-07-02 08:11 UTC to 2026-07-02 15:23 UTC, by the times RudderStack posted.
What was affected?
RudderStack named Data Processing Pipeline (US), Data Processing Pipeline (EU) in eu, 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.