Intermittent failures scheduling warehouse jobs and processing Profile Syncs
Segment reports intermittent failures scheduling warehouse jobs and processing Profile Syncs in Warehouse Destinations (US), Profiles Sync, Warehouses - Warehouse Destinations (US), and Engage - Profiles Sync. The provider now monitors the issue.
State
Monitoring
Started
Ongoing for
1 h 27 min
Worst impact
Partial outage
Timeline
1 updateMonitoring
1 h 27 min 100%
Updates
Times in UTCAs posted by Segment
We are currently monitoring elevated failures scheduling warehouse jobs and processing Profile Syncs.
Affected components
4Segment in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
3 h 11 min
This incident
54% shorter than the median
Other Segment incidents
All incidentsSegment·Delays to Realtime Audiences and Journeys
Segment Engage Realtime Audiences and Journeys in the US had delays. Segment reports that the incident is resolved. The incident lasted 128 minutes.
Segment·Scheduled Database Maintenance
Segment Warehouse Destinations (EU) and Profiles Sync had degraded performance. The EU region also affected the warehouse destinations and Engage profiles sync. Segment reports that the problem is resolved. The outage lasted 9 minutes.
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.
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.
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.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.
https://outages.live/feed.xml?providers=segment/feed subscribe https://outages.live/feed.xml?providers=segmentFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane