- Level
- confirmed
- Worst impact
- Degraded
- Components
- Streaming Destinations (US)
- Regions
- us
- Down Index
- 22of 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 1h 15m it lasted.
Anything that failed between 2026-07-15 16:48 UTC and 2026-07-15 18: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
We are currently investigating an issue impacting the time to first attempt for Connections event delivery.
provider
- identified
have identified the root cause and are actively working on a fix.
provider
- monitoring
Systems are recovering, we're actively monitoring.
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-22203f6646
Is Segment still down?
No, this incident was resolved 2026-07-15 18:03 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
1h 15m, from 2026-07-15 16:48 UTC to 2026-07-15 18:03 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.