Scheduled Database Maintenance in USW2
We will be conducting scheduled maintenance for a critical internal service database on November 11th, 2026 from 6:30 AM UTC to 9:30 AM UTC. This is part of our periodic maintenance to keep our infrastructure up to date. The maintenance will last approximately four hours. During this window, Segment Data Lakes syncs (storage destinations) may be delayed. Syncs will resume automatically once the maintenance is complete, and no data will be lost. We will update this status as soon as the maintenance is completed.
The latest update from Segment.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Segment
We will be conducting scheduled maintenance for a critical internal service database on November 11th, 2026 from 6:30 AM UTC to 9:30 AM UTC. This is part of our periodic maintenance to keep our infrastructure up to date. The maintenance will last approximately four hours. During this window, Segment Data Lakes syncs (storage destinations) may be delayed. Syncs will resume automatically once the maintenance is complete, and no data will be lost. We will update this status as soon as the maintenance is completed.
Affected components
2Segment in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
2 h 15 min
This incident
Not comparable
Other Segment incidents
All incidentsSegment·Intermittent failures scheduling warehouse jobs and processing Profile Syncs
Segment reported intermittent failures that affected Warehouse Destinations (US) and Profiles Sync. The incident is resolved. It lasted 2 hours and 15 minutes.
Segment·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.
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