- Level
- confirmed
- Worst impact
- Degraded
- Components
- Streaming Destinations (US)
- Regions
- us
- Down Index
- 24of 100
What to do
Check whether you use Segment Streaming Destinations (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 2h 45m it lasted.
Anything that failed between 2025-11-11 01:04 UTC and 2025-11-11 03:49 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
Our systems have reported an elevated Time to First Attempt for Connections traffic. We're actively investigating.
provider
- identified
We've identified the cause of the delays and are taking steps to mitigate the elevated delays.
provider
- monitoring
We've mitigated the cause of the delays and are actively monitoring as they recovery.
provider
- resolved
We've confirmed that the delivery time to first attempt has returned to normal levels.
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-ec69b1cc69
Is Segment still down?
No, this incident was resolved 2025-11-11 03:49 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
2h 45m, from 2025-11-11 01:04 UTC to 2025-11-11 03:49 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.