- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-01-26 19:00 UTC and 2026-01-26 19:00 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 1
- resolved
We identified an issue where some destinations, for a subset of customers, in ReverseETL were not accurately reporting their delivery counts. We're currently backfilling the observability data, and all new runs for the affected ReverseETL should now display the correct counts.
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-48e58b844e
Is Segment still down?
No, this incident was resolved 2026-01-26 19:00 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
0m, from 2026-01-26 19:00 UTC to 2026-01-26 19:00 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.