Segment Outage History

Reddit Conversions API destination is operational.

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.

This incident has been resolved.

An 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 Activations for Event Triggered Journeys.

In [`502fd57`](https://github.com/tresl-co/uptime/commit/502fd57b5850107540a994ac0589422cd91b2c1a ), api.tresl.co (https://api.tresl.co/health) was **down**: - HTTP code: 0 - Response time: 0 ms

Apr 13, 12:19 PDT Resolved - The issue impacting Audience Preview functionality has been resolved. Audience Preview is now operating normally. Apr 13, 12:04 PDT Update - We are continuing to investigate this issue. Apr 13, 12:02 PDT Investigating - We are currently investigating an issue where the Audience Previews are not loading for some customers.

Apr 9, 12:53 PDT Resolved - This incident has been resolved. Apr 9, 12:29 PDT Monitoring - A fix has been implemented and Reverse ETL syncs are now proceeding successfully without any failures. We are closely monitoring the recovery process. Apr 9, 11:15 PDT Identified - We've identified the issue and are currently working on mitigating it. Apr 9, 09:40 PDT Investigating - Certain Reverse ETL syncs are experiencing failures. The team is currently investigating the issue.

Apr 7, 11:30 PDT Resolved - We've confirmed that the impacted destinations have recovered. All impacted events will automatically be retried. No further action needed. Apr 7, 10:37 PDT Monitoring - 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. Apr 7, 10:10 PDT Identified - A recent update has been identified as the cause of this issue. We are working on reverting the change. Apr 7, 10:07 PDT Investigating - 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.

Summary: 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 Overview webpage. Notification Update: Some customers may have received automated email notifications citing "Audience Run Failures" during this time. Please be advised that these were false positives triggered by the maintenance; no actual failures occurred, and all background processes completed successfully. Status: Functionality was fully restored and all systems were confirmed stable as of 9:38 AM PST. We apologize for the inconvenience.

Mar 17, 12:39 PDT Resolved - The issue has been resolved, and EU users are now able to access the Audiences overview page in the Segment UI. Mar 17, 11:55 PDT Investigating - 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.

Mar 9, 17:45 PDT Resolved - The issue has been resolved. Mar 9, 15:29 PDT Update - The issue has been mitigated. Mar 9, 13:51 PDT Update - The engineering team is still working on mitigating the issue. Mar 9, 10:18 PDT Update - The engineering team is continuing to work to mitigate the issue. Mar 9, 07:40 PDT Identified - 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.

Mar 4, 22:30 PST Completed - The scheduled maintenance has been completed. Mar 4, 21:30 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar 4, 06:49 PST Scheduled - We will be conducting scheduled maintenance for a critical internal service database on March 5th, 2026 from 5:30 AM - 6:30 AM UTC. This will be performed in EU region and is part of our periodic maintenance to keep our infrastructure up to date. The maintenance will last approximately for an hour. During this window, you may experience some failures across warehouse destinations, cloud sources and profile syncs. We will update this status as soon as the maintenance is completed.

Feb 25, 22:24 PST Resolved - This incident has been resolved. Feb 25, 21:51 PST Monitoring - 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

Feb 6, 23:12 PST Resolved - This incident has been resolved. Feb 6, 16:30 PST Monitoring - We have reverted the change and confirmed that submitting events to Google Tag Manager is working as expected. We will continue to monitor closely. Feb 6, 13:58 PST Identified - 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.

Feb 4, 11:38 PST Completed - The scheduled maintenance has been completed. Feb 4, 11:26 PST Verifying - Verification is currently underway for the maintenance items. Feb 4, 10:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 10:00 PST Scheduled - We will be conducting scheduled maintenance on our Suppression Database. During this maintenance window, customers may experience temporary service degradation. • US: Starting at 07:00 PM UTC on Wednesday, Feb 4, 2026 Affected Services: • Public API: The listSuppressions endpoint will be temporarily unavailable. https://docs.segmentapis.com/tag/Deletion-and-Suppression#operation/listSuppressions • UI: The Suppression list page will be temporarily unavailable. No other Segment products will be impacted.

Feb 3, 12:00 PST Completed - The scheduled maintenance has been completed. Feb 3, 11:54 PST Verifying - Verification is currently underway for the maintenance items. Feb 3, 09:00 PST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb 2, 10:39 PST Update - We will be undergoing scheduled maintenance during this time. Feb 2, 10:38 PST Update - We will be undergoing scheduled maintenance during this time. Feb 3, 10:00 PST Scheduled - We will be conducting scheduled maintenance on our Suppression Database. During this maintenance window, customers may experience temporary service degradation. • EU: Starting at 07:00 PM UTC on Tuesday, Feb 3, 2026 Affected Services: • Public API: The listSuppressions endpoint will be temporarily unavailable. https://docs.segmentapis.com/tag/Deletion-and-Suppression#operation/listSuppressions • UI: The Suppression list page will be temporarily unavailable. No other Segment products will be impacted.

Jan 27, 11:36 PST Resolved - This incident has been resolved. Jan 27, 09:17 PST Monitoring - We’ve identified and resolved a regression affecting observability for a small portion of the LiveRamp and Trade Desk CRM destination delivery. We're monitoring but we resolve this shortly.

We 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 affected ReverseETL should now display the correct counts.

Jan 26, 01:54 PST Resolved - This incident has been resolved. Jan 26, 00:10 PST Monitoring - Tiktok APIs have recovered and we see successful traffic flowing through from Segment. We'll continue to monitor the destination traffic. Jan 25, 09:01 PST Identified - Tiktok's Ad Measurement APIs are returning 500. We have reached out to Tiktok for support. There is widespread Tiktok outage reported. Jan 25, 03:37 PST Investigating - We are currently investigating an issue with Tiktok Offline Conversions and Tiktok Conversions destination. Tiktok Business APIs are experiencing an outage.

Jan 22, 09:37 PST Resolved - This incident has been resolved. Jan 22, 08:02 PST Monitoring - The incident has been mitigated and we are monitoring the destination. We will provide updates as more information becomes available from Yahoo team. Jan 22, 06:36 PST Identified - We are experiencing "504 - Gateway Time-out" errors when communicating with the Yahoo DSP endpoint. We are working with Yahoo support team to get this resolved. We will provide updates as more information becomes available. Jan 22, 05:33 PST Investigating - We are observing elevated ETIMEDOUT errors from Yahoo DSP destination. We are currently investigating the issue.

Jan 9, 13:18 PST Resolved - The issue has been resolved. Jan 9, 13:02 PST Monitoring - The partner has fixed the issue. We are actively monitoring to see if the issue is completely resolved. Jan 9, 12:39 PST Investigating - We are currently investigating the issue.

Dec 16, 08:55 PST Resolved - This incident has been resolved. Dec 16, 00:24 PST Update - We are continuing to investigate this issue. Dec 15, 22:37 PST Investigating - We are currently monitoring the issue . Outage is declared here : https://status.snowflake.com/incidents/xdxj4klf7sc5

Dec 9, 18:28 PST Resolved - Event delivery has returned to normal. Dec 9, 15:42 PST Monitoring - Delays are recovering, and we are actively monitoring the recovery process. Dec 9, 14:11 PST Identified - We've identified the cause and working on mitigating the incident.