- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Streaming Destinations (US)
- Regions
- us
- Down Index
- 35of 100
What to do
Check whether you use Segment Streaming Destinations (US) in us. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 6h 9m it lasted.
Anything that failed between 2025-09-19 03:59 UTC and 2025-09-19 10:08 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 5
- investigating
We are currently investigating this issue.
provider
- investigating
We are continuing to investigate 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.
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-41126ff1e3
Is Segment still down?
No, this incident was resolved 2025-09-19 10:08 UTC. For Segment's live state, see https://down.guide/providers/segment.
How long did it last?
6h 9m, from 2025-09-19 03:59 UTC to 2025-09-19 10:08 UTC, by the times Segment posted.
What was affected?
Segment named Streaming Destinations (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.