Live

Delays to Realtime Audiences and Journeys

0

Segment Engage Realtime Audiences and Journeys in the US have delays. Segment deployed a fix and reports that delays are decreasing. Segment continues to monitor the incident.

State

Monitoring

Started

Ongoing for

1 h 31 min

Worst impact

Degraded

Timeline

4 updates
20:1720:4021:0321:2621:48
DegradedUpdate postedTimes in UTC

Investigating

16 min 17%

Identified

57 min 63%

Monitoring

18 min 20%

Updates

Times in UTC

As posted by Segment

Monitoring

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.

Identified

We are continuing to work on a fix for this issue.

Identified

The issue has been identified and a fix is being implemented.

Investigating

The team is currently investigating an issue causing delay to Engage Realtime Audiences and Journeys.

Affected components

4
Engage (US)Journeys (US)Engage - Engage (US)Engage - Journeys (US)

Segment in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

10

Median duration

4 h 12 min

This incident

64% 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 4 h 12 min
90 days agoToday

Other Segment incidents

All incidents

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.live/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.live/feed.xml?providers=segment
Slack
/feed subscribe https://outages.live/feed.xml?providers=segment

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane