- Level
- confirmed
- Worst impact
- Degraded
- Components
- Web Interface (US), Engage (US)
- Regions
- us
- Down Index
- 27of 100
What to do
Check whether you use Segment Web Interface (US), Engage (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 2d 21h it lasted.
Anything that failed between 2025-09-25 15:40 UTC and 2025-09-28 13:32 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
- identified
We are aware of the issue with Journey Top level analytics and Journey Step level analytics. We are working to bring the feature back online. This does NOT affect journey processing or delivery.
provider
- identified
Journey Analytics are loading, but data will be delayed as we are recovering. There is still NO IMPACT to Journey processing.
provider
- identified
The team continues to work on recovering data, and will provide updates as we progress
provider
- monitoring
Journey Analytics have been restored to near real time processing. We are still in the process of restoring some data from within the past week so some data prior to 9/25 may be inconsistent. We will provide another update when this backfill is complete.
provider
- resolved
All data for journey analytics has been successfully restored and systems are operating normally.
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-785d6189ce
Is Segment still down?
No, this incident was resolved 2025-09-28 13:32 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
2d 21h, from 2025-09-25 15:40 UTC to 2025-09-28 13:32 UTC, by the times Segment posted.
What was affected?
Segment named Web Interface (US), Engage (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.