Segment App UI Issue with Profile Traits with no recent activity
This incident has been resolved.
The latest update from Segment.
State
Resolved
Started
59 d ago
2026-09-03 01:04 UTC
Lasted
21 h 38 min
until 2026-09-03 22:42 UTC
Worst impact
Degraded
Timeline
5 updatesIdentified
19 h 16 min 89%
Monitoring
2 h 22 min 11%
Updates
Times in UTCAs posted by Segment
This incident has been resolved.
A fix has been applied and the Engage UI experience should be fully functional. We are continuing to monitor results.
We are continuing efforts to mitigate this issue.
We are continuing efforts to mitigate this issue.
We have identified an issue that may cause profile traits with no activity in the last 60 days to be unavailable in Audience Builder, trait and event pickers, and related trait detail views for some customers. This is a display issue only; underlying customer event and profile data is not affected.
Affected components
4Segment in the last 90 days
Full historyIncidents in 90 days
10
Days with an incident
10
Median duration
6 h 23 min
This incident
3.4× the median
Other Segment incidents
All incidentsSegment·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.
Segment·Audience & Journey data delivery delay in EU region
This incident has been resolved.
Segment·Braze Web Event Delivery is experience event delivery issue
This incident has been resolved now.
Segment·Actions S3 is currently experience formatting issues with the delivered events
We have resolved the issue now.
Segment·SSO Login Issues with the Segment App
The issue has been mitigated, and SSO login is now fully functional for the Segment app.
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.
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.
https://outages.cc/feed.xml?providers=segment/feed subscribe https://outages.cc/feed.xml?providers=segmentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane