- Level
- confirmed
- Worst impact
- Degraded
- Components
- Engage (EU)
- Regions
- eu
What to do
Check whether you use Segment Engage (EU) in eu. 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 33m it lasted.
Anything that failed between 2025-10-14 20:46 UTC and 2025-10-14 22:18 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 3
- investigating
We are currently seeing delays in event delivery in the EU, our engineering teams have identified and are working to implement a path to resolution.
provider
- monitoring
We have implemented a fix for the event delivery lag, and are monitoring as the delays decrease, and we move towards real-time.
provider
- resolved
Delays have fully recovered to real-time. We have seen no indication of any data loss as part of this incident.
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-adad09061e
Is Segment still down?
No, this incident was resolved 2025-10-14 22:18 UTC. For Segment's live state, see https://down.guide/segment.
How long did it last?
1h 33m, from 2025-10-14 20:46 UTC to 2025-10-14 22:18 UTC, by the times Segment posted.
What was affected?
Segment named Engage (EU) in eu.
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.