Segment reported "Audience & Journey data delivery delay in EU region" on its status page at 2026-10-02 23:12 UTC.

When did the incident start and end?

It started at 2026-10-02 23:12 UTC and ended at 2026-10-03 00:28 UTC. It lasted 1 h 16 min.

How do I get alerts for Segment?

Subscribe to the Segment live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Segment. outages.live reads it every few minutes and keeps every update.

SegmentIncident · 2026-10-02 23:12 UTC

Audience & Journey data delivery delay in EU region

Q: What is affected?

Segment lists these components: Engage (EU), Linked Audiences (EU), Journeys (EU), Engage - Engage (EU), Engage - Journeys (EU), Linked Audiences - Linked Audiences (EU).

ResolvedOfficial update

This incident has been resolved.

The latest update from Segment.

State

Resolved

Started

30 d ago

2026-10-02 23:12 UTC

Lasted

1 h 16 min

until 2026-10-03 00:28 UTC

Worst impact

Degraded

Timeline

2 updates

23:1223:3123:5000:0900:28

DegradedUpdate postedTimes in UTC

Identified

1 h 16 min 100%

Updates

Times in UTC

As posted by Segment

Resolved2026-10-03 00:28 UTC

This incident has been resolved.

Identified2026-10-02 23:12 UTC

We have identified an issue affecting a small portion of Audience & Journey delivery resulting in data delay.

Affected components

Engage (EU)Linked Audiences (EU)Journeys (EU)Engage - Engage (EU)Engage - Journeys (EU)Linked Audiences - Linked Audiences (EU)

Segment in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

6 h 23 min

This incident

80% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 h 38 min

median 6 h 23 min

90 days agoToday

Other Segment incidents

All incidents

Segment·Segment event delivery issues

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.

Resolvedresolved 6 d ago

Segment·Braze Web Event Delivery is experience event delivery issue

This incident has been resolved now.

Resolvedresolved 31 d ago

Segment·Actions S3 is currently experience formatting issues with the delivered events

We have resolved the issue now.

Resolvedresolved 46 d ago

Segment·SSO Login Issues with the Segment App

The issue has been mitigated, and SSO login is now fully functional for the Segment app.

Resolvedresolved 52 d ago

Segment·Issue with Engage UI

This incident has been resolved.

Resolvedresolved 59 d ago

Follow Segment

Your coding agent knows when Segment is down, and tells you when a failure is theirs, not yours. You can also get Segment incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "segment" and tell me if Segment has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=segment

Slack

/feed subscribe https://outages.cc/feed.xml?providers=segment

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane