Segment: Delays to Realtime Audiences and Journeys

What to do

Check whether you use Segment Engage (US), Journeys (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 2h 8m it lasted.
Anything that failed between 2026-11-04 20:17 UTC and 2026-11-04 22:25 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.

investigatingNov 4, 2026, 8:17 PM UTC
The team is currently investigating an issue causing delay to Engage Realtime Audiences and Journeys.
provider
identifiedNov 4, 2026, 8:30 PM UTC
The issue has been identified and a fix is being implemented.
provider
identifiedNov 4, 2026, 9:04 PM UTC
We are continuing to work on a fix for this issue.
provider
monitoringNov 4, 2026, 9:28 PM UTC
A fix has been deployed and we are seeing delays decrease. We are continuing to monitor and will post another update as we monitor towards resolution.
provider
resolvedNov 4, 2026, 10:25 PM UTC
This incident has been resolved.
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-11-04 22:25 UTC. For Segment's live state, see https://down.guide/segment.

How long did it last?

2h 8m, from 2026-11-04 20:17 UTC to 2026-11-04 22:25 UTC, by the times Segment posted.

What was affected?

Segment named Engage (US), Journeys (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.