Segment Outage History

This incident has been resolved.

This incident is resolved now

We are currently deploying the fix to mitigate the issue

This incident has been resolved

Systems are recovering, we're actively monitoring.

have identified the root cause and are actively working on a fix.

We are currently investigating an issue impacting the time to first attempt for Connections event delivery.

This incident has been resolved. Traffic is flowing through to Criteo APIs

We are currently seeing successful delivery to Criteo. Our team will continue to monitor the closely.

We are currently experiencing disruptions with Criteo Audience destinations due to an external Criteo API outage. We are monitoring the situation closely.

This incident has been resolved.

We've shipped a fix and confirmed that it’s working. We’re going to keep a close eye on things for the next few hours just to be absolutely sure everything is stable.

The root cause has been identified. will be rolling out the fix shortly.

The root cause has been identified. will be rolling out the fix shortly.

Reddit Conversions API destination is operational.

Events are flowing through to Reddit Conversions API destination now. We are continuing to monitor the destination.

We are currently observing delivery failures with the Reddit Conversions API destination. This issue stems from a widespread AWS outage (us-east-1) affecting Reddit’s infrastructure. We are monitoring the situation closely and will provide updates as Reddit restores service.

This incident has been resolved.

The issue is now mitigated. We’ve deployed a fix, and the Destinations page is loading as expected for all workspaces that were previously impacted. We are monitoring the results.

We’ve identified the root cause and are currently implementing a fix. The issue is isolated to a subset of workspaces with connected RETL destinations.

We are currently investigating an issue affecting the Destinations page in the Segment application UI. For some customers, the Destinations are failing to load.

Summary: 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 infrastructure failure at Databricks, which prevented some preview queries from executing successfully. This issue was localized to the dashboard preview tool; real-time event delivery and audience activations were not impacted. Resolution: The underlying compute issue has been resolved by the vendor. We have confirmed that preview functionality is fully restored and operating normally.

We've confirmed that the impacted destinations have recovered. All impacted events will automatically be retried. No further action needed.

A fix has been implemented, and we are seeing initial signs of recovery. We will continue to monitor the service closely to ensure full stability.

A recent update has been identified as the cause of this issue. We are working on reverting the change.

Amazon Event Bridge and Amazon Personalize Destinations are experiencing elevated error rates. We are currently investigating the issue. We will provide updates as they become available.

Engineering 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.

The issue has been resolved, and EU users are now able to access the Audiences overview page in the Segment UI.

Engineering is currently investigating an issue that is preventing customers in the EU from viewing Audiences overview pages in the Segment UI. This issue is limited to the UI only and does not impact the data plane.

The issue has been resolved.

The issue has been mitigated.

The engineering team is still working on mitigating the issue.

The engineering team is continuing to work to mitigate the issue.

Segment users may experience slow loading and intermittent UI errors on Audiences and Journeys pages. The team has identified the root cause of the issue and is working now to mitigate the issue.

This incident has been resolved.

The Marketo source syncs are failing as Marketo APIs are down. Expect a failure in syncs and a delay in data processing. Official Abobe Marketo page to track the API availability:- https://status.adobe.com/products/503491

This incident has been resolved.

We have reverted the change and confirmed that submitting events to Google Tag Manager is working as expected. We will continue to monitor closely.

We have identified an issue where Google Tag Manager doesn't initialize correctly from the latest version of Analytics.js. We've identified the cause and have deployed a fix, which will deploy across the CDN over the next few hours.

This incident has been resolved.

Tiktok APIs have recovered and we see successful traffic flowing through from Segment. We'll continue to monitor the destination traffic.

Tiktok's Ad Measurement APIs are returning 500. We have reached out to Tiktok for support. There is widespread Tiktok outage reported.

We are currently investigating an issue with Tiktok Offline Conversions and Tiktok Conversions destination. Tiktok Business APIs are experiencing an outage.

The issue has been resolved.

The partner has fixed the issue. We are actively monitoring to see if the issue is completely resolved.

We are currently investigating the issue.

Event delivery has returned to normal.

Delays are recovering, and we are actively monitoring the recovery process.

We've identified the cause and working on mitigating the incident.

We've confirmed that the impacted destinations have recovered.

We are continuing to monitor for any further issues.

All impacted destinations have recovered and normal operations have resumed. We will continue to monitor closely.

We are observing early signs of success. We will continue to monitor.

We have identified the root cause of the incident and we are working towards a fix.

We are observing elevated errors in the following Facebook destinations (actions-facebook-conversions-api, actions-facebook-custom-audiences, facebook-app-events, facebook-offline-conversions, facebook-pixel-server-side, personas-facebook-ads).

Delivery 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.

A subset of events are delayed delivering to destinations by approximately 1 hour. The team has mitigated the root cause, and is monitoring as delivery time returns to normal.

We've confirmed that the delivery time to first attempt has returned to normal levels.

We've mitigated the cause of the delays and are actively monitoring as they recovery.

We've identified the cause of the delays and are taking steps to mitigate the elevated delays.

Our systems have reported an elevated Time to First Attempt for Connections traffic. We're actively investigating.

We've restored the ReverseETL delivery counts in the US

We've restored the ReverseETL delivery counts in the EU and are actively working on updating them in the US.

We’re actively working on retroactively updating the ReverseETL delivery counts for affected customers. All ReverseETL Syncs created after 4 PM PST will correctly report counts.

ReverseETL delivery counts are currently delayed. Syncs that started between 6:00 AM and 4:00 PM PST on November 3 may show inaccurate counts or timeout errors. We've identified the issue and are working towards a resolution. Note: This is only affecting reporting, no data loss or change in delivery.

Intercom cloud sources data fetching issues have been resolved. All services are now operating normally.

Intercom EU cloud sources are now fully operational and data ingestion has been restored. All services are functioning normally

We are monitoring the recovery of Intercom cloud sources after experiencing data fetching issues. Intercom has reported their services are recovering from the incident. We are closely watching data ingestion to ensure full restoration.

Segment is observing service unavailable error from intercom APIs.

Delays have fully recovered to real-time. We have seen no indication of any data loss as part of this incident.

We have implemented a fix for the event delivery lag, and are monitoring as the delays decrease, and we move towards real-time.

We are currently seeing delays in event delivery in the EU, our engineering teams have identified and are working to implement a path to resolution.

After thorough monitoring and analysis, we have determined that this issue did not impact customers.

Delays in production in the eu-west-1 region have returned to normal. We're actively monitoring.

Segment p99 delivery latency is elevated above slightly above 5 minutes. We're actively investigating.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

We've applied a fix and are waiting for traffic to recover.

We've identified delivery delays of up to 10 minutes for some customers.

All data for journey analytics has been successfully restored and systems are operating normally.

Journey Analytics have been restored to near real time processing. We are still in the process of restoring some data from within the past week so some data prior to 9/25 may be inconsistent. We will provide another update when this backfill is complete.

The team continues to work on recovering data, and will provide updates as we progress

Journey Analytics are loading, but data will be delayed as we are recovering. There is still NO IMPACT to Journey processing.

We are aware of the issue with Journey Top level analytics and Journey Step level analytics. We are working to bring the feature back online. This does NOT affect journey processing or delivery.

This incident has been resolved.

A fix has been implemented and we are monitoring the results

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented

We are investigating an issue causing delays in cloud sources data sync.

This incident has been resolved.

We are continuing to monitor for any further issues.

We've mitigated this incident, and impacted customers should start seeing positive results.

We've identified the cause of the forbidden errors and are working on mitigation.

We're investigating unexpected forbidden errors across multiple customers for the google enhanced conversions destination. We're reaching out to Google for support.

The incident is now fully resolved.

We are monitoring recovery and expect Reverse ETL delivery statistics to be fully caught up in approximately 6 hours.

Updates to Reverse ETL delivery statistics and sync status have been delayed since approximately 3pm PT on 8/14. Delivery of actual messages is unaffected.

All events are flowing through now

The delivery endpoint is up now. We are monitoring

Clearbit Reveal integration is facing delivery issues. Clearbit integration endpoint is down. We have reached out to Clearbit for help.

This incident has been resolved.

Due to rate limiting by our upstream infrastructure vendor, we are seeing delays of 30 minutes in Predictive Recommendations, and in delivery of audiences and computed traits to List Destinations. We are monitoring these delays as they recover.

This incident has been resolved.

Delays are caught up and we are continuing to monitor

We are continuing to investigate this issue.

Delayed updates on audience and compute traits computations running on batch system from 2AM PST

This incident has been resolved.

We continue to monitor queue recovery, and expect delays to recover within the hour.

A subset of Linked & Batch Audiences computations are be taking longer than normal to complete.