Live / Segment / Incident
Segment: Delays to Realtime Audiences and Journeys
Segment · segment.comMinor incidentResolved2026-11-04 22:25 UTC
Public — what happened
Summary
Segment said it began investigating at 20:17 UTC on 2026-11-04 after delays affected its Engage Realtime Audiences and Journeys features, which it rated as a minor issue. By 20:30 UTC the company said it had identified the problem and was working on a fix. At 21:28 UTC Segment reported that a fix was in place and delays were shrinking while it kept watching, and the incident was marked resolved at 22:25 UTC.
Affected
Engage (US), Journeys (US)
Timeline
- Started — 2026-11-04 20:17 UTC
- Investigating — 2026-11-04 20:17 UTC
- Identified — 2026-11-04 20:30 UTC (2 updates)
- Monitoring — 2026-11-04 21:28 UTC
- Resolved — 2026-11-04 22:25 UTC · 2h 08m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Segment against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Segment: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Segment report →
More from Segment
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.