- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing Pipeline (US)
- Regions
- us
- Down Index
- 27of 100
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 11h 1m it lasted.
Anything that failed between 2025-07-02 16:30 UTC and 2025-07-03 03:30 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
- investigating
We are currently investigating this issue.
provider
- resolved
Deliveries to Google Ads Offline Conversions were impacted due to issues (unavailable, high latency and unexpected behavior) with Google Ads API as reported by Google (https://ads.google.com/status/publisher/incidents/xF9wKox7evao5WupR7mu). We’ve identified the affected customers and have completed a replay for all impacted destinations.
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-d08adde837
Is RudderStack still down?
No, this incident was resolved 2025-07-03 03:30 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
11h 1m, from 2025-07-02 16:30 UTC to 2025-07-03 03:30 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.