outages.live
Live
SegmentIncident · 2026-08-06 05:50 UTC

Notification and verification email delivery

ResolvedOfficial update

This incident has been resolved.

The latest update from Segment.

State

Resolved

Started

87 d ago

2026-08-06 05:50 UTC

Lasted

12 h 5 min

until 2026-08-06 17:55 UTC

Worst impact

Notice

Timeline

3 updates
05:5008:5111:5214:5317:55
NoticeUpdate postedTimes in UTC

Investigating

1 h 32 min 13%

Monitoring

10 h 34 min 87%

Updates

Times in UTC

As posted by Segment

Resolved2026-08-06 17:55 UTC

This incident has been resolved.

Monitoring2026-08-06 07:21 UTC

A fix has been implemented and we are monitoring the results.

Investigating2026-08-06 05:50 UTC

We are currently investigating an issue where security code verification notifications may not be delivered via email.

Segment in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

10

Days with an incident

10

Median duration

6 h 23 min

This incident

1.9× 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·Audience & Journey data delivery delay in EU region

This incident has been resolved.

Resolvedresolved 29 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

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