- Level
- confirmed
- Worst impact
- Degraded
- Components
- Streaming Destinations (US), Engage (US), Streaming Destinations (EU), Engage (EU), Profiles Sync, Journeys (US), Journeys (EU)
- Regions
- eu, us
- Down Index
- 27of 100
What to do
Check whether you use Segment Streaming Destinations (US), Engage (US), Streaming Destinations (EU), Engage (EU) and 3 more in eu, 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 10m it lasted.
Anything that failed between 2026-09-16 19:40 UTC and 2026-09-16 21:50 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 2
- investigating
We are currently investigating an issue causing formatting anomalies with S3 action destinations. Our team is working on a mitigation.
provider
- resolved
We have resolved the issue now.
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-52bf7c3341
Is Segment still down?
No, this incident was resolved 2026-09-16 21:50 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
2h 10m, from 2026-09-16 19:40 UTC to 2026-09-16 21:50 UTC, by the times Segment posted.
What was affected?
Segment named Streaming Destinations (US), Engage (US), Streaming Destinations (EU), Engage (EU) and 3 more in eu, 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.