Segment had 55 outages in the last 2 years totaling 149h 38m of downtime — averaging 2.3 incidents per month.
There were 55 Segment outages since May 28, 2025 totaling 149h 38m of downtime. Each is summarised below — incident details, duration, and resolution information.
In [`d77f221`](https://github.com/tresl-co/uptime/commit/d77f2213dea2504be6a1be287d761508613fa155 ), www.tresl.co (https://www.tresl.co) was **down**: - HTTP code: 500 - Response time: 144 ms
Nov 23, 21:04 PST Resolved - We've confirmed that the impacted destinations have recovered. Nov 23, 20:50 PST Update - We are continuing to monitor for any further issues. Nov 23, 20:50 PST Update - All impacted destinations have recovered and normal operations have resumed. We will continue to monitor closely. Nov 23, 19:53 PST Monitoring - We are observing early signs of success. We will continue to monitor. Nov 23, 19:20 PST Identified - We have identified the root cause of the incident and we are working towards a fix. Nov 23, 17:47 PST Investigating - 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).
Nov 20, 17:21 PST Resolved - 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. Nov 20, 16:38 PST Monitoring - 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.
Nov 10, 19:49 PST Resolved - We've confirmed that the delivery time to first attempt has returned to normal levels. Nov 10, 19:32 PST Monitoring - We've mitigated the cause of the delays and are actively monitoring as they recovery. Nov 10, 17:45 PST Identified - We've identified the cause of the delays and are taking steps to mitigate the elevated delays. Nov 10, 17:04 PST Investigating - Our systems have reported an elevated Time to First Attempt for Connections traffic. We're actively investigating.
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.
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.
We've restored the ReverseETL delivery counts in the EU and are actively working on updating them in the US.
We've restored the ReverseETL delivery counts in the US
Segment is observing service unavailable error from intercom APIs.
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.
Intercom EU cloud sources are now fully operational and data ingestion has been restored. All services are functioning normally
Intercom cloud sources data fetching issues have been resolved. All services are now operating normally.
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.
We have implemented a fix for the event delivery lag, and are monitoring as the delays decrease, and we move towards real-time.
Delays have fully recovered to real-time. We have seen no indication of any data loss as part of this incident.
Segment p99 delivery latency is elevated above slightly above 5 minutes. We're actively investigating.
Delays in production in the eu-west-1 region have returned to normal. We're actively monitoring.
After thorough monitoring and analysis, we have determined that this issue did not impact customers.
We are currently investigating this issue.
This incident has been resolved.
We've identified delivery delays of up to 10 minutes for some customers.
We've applied a fix and are waiting for traffic to recover.
This incident has been resolved.
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.
Journey Analytics are loading, but data will be delayed as we are recovering. There is still NO IMPACT to Journey processing.
The team continues to work on recovering data, and will provide updates as we progress
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.
All data for journey analytics has been successfully restored and systems are operating normally.
We are investigating an issue causing delays in cloud sources data sync.
The issue has been identified and a fix is being implemented
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Between August 28, 2025, 11:21 AM PT and September 5, 2025, 5:04 AM PT, certain internal computed traits were unintentionally synced to the profile_traits_updates raw table for some specific scenarios. This resulted in partial sync failures for that table because of a breach of the warehouse column limit, which prevented data from being fully written. To mitigate the issue, we have disabled the syncing of such traits going forward and are actively evaluating next steps to remediate the data that was already synced.
We 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 customers on how to address any previously affected data.
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.
We are monitoring recovery and expect Reverse ETL delivery statistics to be fully caught up in approximately 6 hours.
The incident is now fully resolved.
Segment deletion calls in US and EU environments have started failing from Aug 14th 4:42AM PST. We are currently investigating the issue
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has now been resolved. All deletion requests are processing successfully
In [`6370026`](https://github.com/tresl-co/uptime/commit/63700268beeba2bc49a74ce2effeed4d62b77201 ), segments.app (https://segments.app) was **down**: - HTTP code: 0 - Response time: 0 ms
Clearbit Reveal integration is facing delivery issues. Clearbit integration endpoint is down. We have reached out to Clearbit for help.
The delivery endpoint is up now. We are monitoring
All events are flowing through now
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.
Delayed updates on audience and compute traits computations running on batch system from 2AM PST
We are continuing to investigate this issue.
Delays are caught up and we are continuing to monitor
This incident has been resolved.
We identified an issue with creating warehouse destinations for warehouse types other than Snowflake. A fix has been implemented and our team is monitoring the results.
This incident has been resolved.
A subset of Linked & Batch Audiences computations are be taking longer than normal to complete.
We continue to monitor queue recovery, and expect delays to recover within the hour.
This incident has been resolved.
We are currently investigating the issue, in partnership with Google support.
This incident has been resolved.
We have observed an increase in latency within Engage and are currently investigating the issue. Audience, Computed Trait, and Journey updates may have been delayed by up to two hours.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue that is impacting syncs for Azure Synapse Analytics warehouse destinations and Profiles Syncs. We are working on a solution.
This incident has been resolved.