Live

Scheduled Database Maintenance

0

Segment Warehouse Destinations (EU) and Profiles Sync are degraded. This includes Warehouses - Warehouse Destinations (EU) and Engage - Profiles Sync. Segment reports that the incident is resolved. It lasted 9 minutes.

State

Resolved

Started

Lasted

9 min

Worst impact

Degraded

Timeline

2 updates
09:2709:2909:3109:3309:36
DegradedUpdate postedTimes in UTC

Investigating

9 min 100%

Updates

Times in UTC

As posted by Segment

Resolved
Investigating

We will be conducting scheduled maintenance for a critical internal service database on November 5th, 2026 from 9:30 AM UTC - 11 AM UTC. This will be performed in the EU region and is part of our periodic maintenance to keep our infrastructure up to date. The maintenance will last approximately for an hour and a half. During this window, you may experience some failures across warehouse destinations, and profiles sync (the syncs may get delayed). We will update this status as soon as the maintenance is completed.

Affected components

4
Warehouse Destinations (EU)Profiles SyncWarehouses - Warehouse Destinations (EU)Engage - Profiles Sync

Segment in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

10

Median duration

4 h 13 min

This incident

96% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 h 38 min
median 4 h 13 min
90 days agoToday

Other Segment incidents

All incidents

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