- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 23of 100
What to do
Check whether your product depends on Segment. 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 28d 1h it lasted.
Anything that failed between 2026-06-05 08:11 UTC and 2026-07-03 09:37 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 root cause has been identified. will be rolling out the fix shortly.
provider
- identified
The root cause has been identified. will be rolling out the fix shortly.
provider
- monitoring
We've shipped a fix and confirmed that it’s working. We’re going to keep a close eye on things for the next few hours just to be absolutely sure everything is stable.
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-723cd67fbf
Is Segment still down?
No, this incident was resolved 2026-07-03 09:37 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
28d 1h, from 2026-06-05 08:11 UTC to 2026-07-03 09:37 UTC, by the times Segment posted.
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.