Segment Outage History

52 incidents recorded over the last 365 days, 43 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Segment status99.43% uptime history

Every Recorded Segment Incident

Segment incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 18, 2026Intermittent Segment application login errorsThis incident has been resolved.4h 13mResolved
Aug 6, 2026Google ads destination intermittent delivery failureThis incident has been resolved.14h 43mResolved
Aug 6, 2026Notification and verification email deliveryThis incident has been resolved.12h 5mResolved
Jul 26, 2026Data processing pipeline issueThis incident has been resolved.2h 27mResolved
Jul 25, 2026Connections Processing DelaysThis incident is now recovered.5h 53mResolved
Jul 18, 2026Scheduled Database Maintenance in USW2The scheduled maintenance has been completed.1h 0mScheduled
Jul 15, 2026Elevated Event Delivery LatencyThis incident has been resolved1h 14mResolved
Jul 11, 2026Scheduled Database Maintenance in EUW1The scheduled maintenance has been completed.1h 0mScheduled
Jul 3, 2026Criteo Audience destinations are experiencing an outageThis incident has been resolved. Traffic is flowing through to Criteo APIs1h 4mResolved
Jun 22, 2026(US West 2) Partial degradation of Linked Audiences, Linked Events, Reverse ETL, and Profile Sync due to external Snowflake OutageSnowflake outage has resolved and consequently impacted functionalities across segment have recovered as well.2h 7mResolved
Jun 5, 2026Facebook Custom Audiences destination is experiencing partial delivery failures for few workspacesThis incident has been resolved.673h 25mResolved
May 8, 2026Reddit Conversions API destination is experiencing delivery failuresReddit Conversions API destination is operational.3h 24mResolved
Apr 29, 2026Audience Preview FailuresSummary: From 10:20 AM to 3:00 PM PDT on April 27th, a global Databricks Compute outage resulted in failed audience preview queries across external workspaces. Details: The disruption was caused by an upstream…-2894 minResolved
Apr 29, 2026Destinations Failing to Load in UIThis incident has been resolved.4h 28mResolved
Apr 27, 2026Unable to add Activation to Event Triggered JourneyAn issue impacting the Event Triggered Journey user interface in the application has been resolved. Prior to resolution, customers may have experienced an error in the user interface impacting their ability to configure…-33 minResolved
Apr 23, 2026Scheduled Database Upgrade in EU regionWe will be conducting scheduled maintenance for a critical internal service database on Th April 23rd, 2026 from 12:30 PM - 1:30 PM PST. This will be performed in EU region and is part of our periodic maintenance to…1h 0mScheduled
Apr 13, 2026Audience Preview UnavailableThe issue impacting Audience Preview functionality has been resolved. Audience Preview is now operating normally.16 minResolved
Apr 9, 2026Reverse ETL syncs experiencing partial disruptionsThis incident has been resolved.3h 12mResolved
Apr 7, 2026Amazon Event Bridge and Amazon Personalize Destinations are experiencing elevated error ratesWe've confirmed that the impacted destinations have recovered. All impacted events will automatically be retried. No further action needed.1h 23mResolved
Mar 31, 2026Resolved: Linked Audiences Traits not selectable in builder UIEngineering team has investigated and resolved an issue related to the Linked Audience Builder. Specifically, traits could not be selected. This is now resolved as of 4:43 PM UTC.-64 minResolved
Mar 19, 2026Audience Overview Page DegradationSummary: Between 9:24 AM PST on March 19 and 9:38 AM PST on March 19, the engineering team performed a database upgrade. During this window, users may have experienced degraded performance specifically on the Audiences…0 minResolved
Mar 17, 2026Audiences Overview Pages are Failing to Load in the EUThe issue has been resolved, and EU users are now able to access the Audiences overview page in the Segment UI.44 minResolved
Mar 9, 2026Degraded performance in Audiences and Journeys UIThe issue has been resolved.10h 5mResolved
Mar 5, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 28, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Feb 26, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 26, 2026Marketo Cloud Source Sync DelayThis incident has been resolved.32 minResolved
Feb 19, 2026Scheduled Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 6, 2026Analytics.js Google Tag Manager issueThis incident has been resolved.9h 13mResolved
Feb 4, 2026Suppression Database Maintenance (US)The scheduled maintenance has been completed.3h 0mScheduled
Feb 3, 2026Suppression Database Maintenance (EU)The scheduled maintenance has been completed.6h 0mScheduled
Jan 27, 2026Degraded LiveRamp & The Trade Desk CRM ObservabilityThis incident has been resolved.2h 19mResolved
Jan 26, 2026Inaccurate Delivery Counts for some ReverseETL Sync ReportsWe identified an issue where some destinations, for a subset of customers, in ReverseETL were not accurately reporting their delivery counts. We're currently backfilling the observability data, and all new runs for the…0 minResolved
Jan 25, 2026Tiktok Conversion Destinations are experiencing an outageThis incident has been resolved.22h 17mResolved
Jan 22, 2026We are observing elevated ETIMEDOUT errors from Yahoo DSP destination.This incident has been resolved.4h 3mResolved
Jan 9, 2026We are currently investigating the issue. The API endpoint at Intercom is returning timeout errors.The issue has been resolved.39 minResolved
Dec 16, 2025Snowflake RETL sources and Warehouse Destinations are failing due to Snowflake OutageThis incident has been resolved.10h 17mResolved
Dec 9, 2025Event delivery is delayedEvent delivery has returned to normal.4h 16mResolved
Nov 24, 2025Elevated errors in Facebook DestinationsWe've confirmed that the impacted destinations have recovered.3h 16mResolved
Nov 21, 2025Delays in Delivery to Destinations for a subset of eventsDelivery latency has returned to normal for all incoming traffic. A small number of events are queued for retry, and will be delivered within the next 15 minutes.42 minResolved
Nov 11, 2025Connections delivery time to first attempt is elevatedWe've confirmed that the delivery time to first attempt has returned to normal levels.2h 45mResolved
Nov 4, 2025Delayed delivery reporting for ReverseETLWe've restored the ReverseETL delivery counts in the US16h 47mResolved
Oct 20, 2025Intercom cloud sources failing to fetch dataIntercom cloud sources data fetching issues have been resolved. All services are now operating normally.14h 19mResolved
Oct 14, 2025Delays in event delivery in EUDelays have fully recovered to real-time. We have seen no indication of any data loss as part of this incident.1h 32mResolved
Oct 9, 2025elevated delivery latency in eu-west-1After thorough monitoring and analysis, we have determined that this issue did not impact customers.1h 12mResolved
Oct 5, 2025Tracking API experiencing degraded experience in US-WestThis incident has been resolved.19 minResolved
Oct 2, 2025Elevated delivery delays for some customersThis incident has been resolved.1h 26mResolved
Sep 25, 2025Journey Analytics are failing to loadAll data for journey analytics has been successfully restored and systems are operating normally.69h 52mResolved
Sep 24, 2025Cloud Source Sync DelayThis incident has been resolved.3h 0mResolved
Sep 19, 2025Google Enhanced Conversions is experiencing elevated failuresThis incident has been resolved.6h 9mResolved
Sep 17, 2025Google Enhanced Conversions is experiencing elevated failuresThis incident has been resolved.3h 28mResolved
Sep 9, 2025Partial Sync Failures for Profiles SyncWe have implemented measures to prevent unintended traits from appearing in profile syncs, and syncs are now running as expected. Our teams are developing a long-term solution and will share guidance with impacted…7h 19mResolved

How to Read This Segment Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Segment acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Segment outage in this window ran 28d 1h, against a mean recovery of 19h 15m. If you depend on Segment in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.