Segment: Segment event delivery issues

What to do

Check whether you use Segment Streaming Destinations (US), Reverse ETL (EU), Streaming Destinations (EU), Reverse ETL (US) 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 16h 20m it lasted.
Anything that failed between 2026-10-26 00:30 UTC and 2026-10-26 16: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.

investigatingOct 26, 2026, 12:30 AM UTC
We have identified that a small no of event delivery is failing. We are currently investigating the issue.
provider
investigatingOct 26, 2026, 12:31 AM UTC
We are continuing to investigate this issue.
provider
resolvedOct 26, 2026, 4:50 PM UTC
We've identified and mitigated the cause of the event delivery issues that affected a small number of customers. If your workspace was affected, please contact Support to request a replay.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Segment still down?

No, this incident was resolved 2026-10-26 16:50 UTC. For Segment's live state, see https://down.guide/segment.

How long did it last?

16h 20m, from 2026-10-26 00:30 UTC to 2026-10-26 16:50 UTC, by the times Segment posted.

What was affected?

Segment named Streaming Destinations (US), Reverse ETL (EU), Streaming Destinations (EU), Reverse ETL (US) 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.