outages.live
Live

Segment

Segment is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

10

Days with an incident

10

Median duration

6 h 23 min

Longest incident

21 h 38 min

Components

34

Data Ingestion (Tracking) API

Data Ingestion (Tracking) API (US) Operational
90 days agoNo incidentsToday
Data Ingestion (Tracking) API (EU) Operational
90 days agoNo incidentsToday

Web Interface

Web Interface (US) Operational
90 days ago3 days with an incidentToday
Web Interface (EU) Operational
90 days ago2 days with an incidentToday

Analytics.js CDN

Analytics.js CDN (US) Operational
90 days agoNo incidentsToday
Analytics.js CDN (EU) Operational
90 days agoNo incidentsToday

Streaming Destinations

Streaming Destinations (US) Operational
90 days ago5 days with an incidentToday
Streaming Destinations (EU) Operational
90 days ago5 days with an incidentToday

Cloud Sources

Cloud Sources (US) Operational
90 days agoNo incidentsToday
Cloud Sources (EU) Operational
90 days agoNo incidentsToday

Warehouses

Warehouse Destinations (US) Operational
90 days agoNo incidentsToday
Warehouse Destinations (EU) Operational
90 days agoNo incidentsToday

Libraries

Libraries (US) Operational
90 days agoNo incidentsToday
Libraries (EU) Operational
90 days agoNo incidentsToday

Engage

Engage (US) Operational
90 days ago2 days with an incidentToday
Engage (EU) Operational
90 days ago3 days with an incidentToday
Profiles Sync Operational
90 days ago1 day with an incidentToday
Journeys (US) Operational
90 days ago1 day with an incidentToday
Journeys (EU) Operational
90 days ago3 days with an incidentToday

Data Processing Pipeline

Data Processing Pipeline (US) Operational
90 days agoNo incidentsToday
Data Processing Pipeline (EU) Operational
90 days agoNo incidentsToday

Public API

Public API (US) Operational
90 days agoNo incidentsToday
Public API (EU) Operational
90 days agoNo incidentsToday

Blobstore Destinations

Blobstore Destinations (US) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration16 h 20 min00:30 to 16:50Segment event delivery issuesDegraded

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.

Oct 2, 2026

Duration1 h 16 min23:12 to 00:28Audience & Journey data delivery delay in EU regionDegraded

This incident has been resolved.

Oct 1, 2026

Duration8 h 33 min03:30 to 12:03Braze Web Event Delivery is experience event delivery issueDegraded

This incident has been resolved now.

Sep 16, 2026

Duration2 h 10 min19:40 to 21:50Actions S3 is currently experience formatting issues with the delivered eventsDegraded

We have resolved the issue now.

Sep 10, 2026

Duration1 h 11 min14:28 to 15:39SSO Login Issues with the Segment AppPartial outage

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

Sep 3, 2026

Duration4 h 11 min18:30 to 22:41Issue with Engage UIPartial outage

This incident has been resolved.

Duration21 h 38 min01:04 to 22:42Segment App UI Issue with Profile Traits with no recent activityDegraded

This incident has been resolved.

Aug 18, 2026

Duration4 h 13 min17:49 to 22:02Intermittent Segment application login errorsPartial outage

This incident has been resolved.

Aug 6, 2026

Duration14 h 44 min15:19 to 06:02Google ads destination intermittent delivery failureDegraded

This incident has been resolved.

Duration12 h 5 min05:50 to 17:55Notification and verification email deliveryNotice

This incident has been resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane