- Level
- confirmed
- Worst impact
- Degraded
- Components
- Streaming Destinations (US), Streaming Destinations (EU)
- Regions
- eu, us
- Down Index
- 30of 100
What to do
Check whether you use Segment Streaming Destinations (US), Streaming Destinations (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 8h 33m it lasted.
Anything that failed between 2026-10-01 03:30 UTC and 2026-10-01 12:03 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 4
- investigating
The issue is reported by one customer. We are investigation this issue.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved now.
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-f96f319426
Is Segment still down?
No, this incident was resolved 2026-10-01 12:03 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
8h 33m, from 2026-10-01 03:30 UTC to 2026-10-01 12:03 UTC, by the times Segment posted.
What was affected?
Segment named Streaming Destinations (US), Streaming Destinations (EU) in eu, 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.