- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Processing Pipeline (US)
- Regions
- us
- Down Index
- 25of 100
What to do
Check whether you use Segment 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 4h 17m it lasted.
Anything that failed between 2025-12-09 22:11 UTC and 2025-12-10 02:28 UTC may need a replay.Subscribe to Segment's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=segment works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Segment 3
- identified
We've identified the cause and working on mitigating the incident.
provider
- monitoring
Delays are recovering, and we are actively monitoring the recovery process.
provider
- resolved
Event delivery has returned to normal.
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-8f60f25e2c
Is Segment still down?
No, this incident was resolved 2025-12-10 02:28 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
4h 17m, from 2025-12-09 22:11 UTC to 2025-12-10 02:28 UTC, by the times Segment posted.
What was affected?
Segment named Data Processing Pipeline (US) in us.
What caused it?
Segment hasn't published a root cause. If it does, it shows here.
Where does this come from?
Segment's official status page, https://status.segment.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.