- Level
- confirmed
- Worst impact
- Major outage
- Components
- Data Ingestion (US)
- Regions
- us
What to do
Check whether you use RudderStack Data Ingestion (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 18m it lasted.
Anything that failed between 2026-05-08 03:44 UTC and 2026-05-08 04:02 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 3
- investigating
We are currently investigating the issue. Enterprise customers are NOT affected by this issue.
provider
- investigating
AWS is having a major issue with load balancers which is also affecting our ingestion layer. We are working to fix the issue.
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-176762222d
Is RudderStack still down?
No, this incident was resolved 2026-05-08 04:02 UTC. For RudderStack's live state, see https://down.guide/rudderstack.
How long did it last?
18m, from 2026-05-08 03:44 UTC to 2026-05-08 04:02 UTC, by the times RudderStack posted.
What was affected?
RudderStack named Data Ingestion (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.