Segment

Affected: Engage (EU), Linked Audiences (EU), Journeys (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-02 23:12 UTC

   We have identified an issue affecting a small portion of Audience & Journey delivery resulting in data delay.

2. resolved 2026-10-03 00:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-01 03:30 UTC

   The issue is reported by one customer. We are investigation this issue.

2. identified 2026-10-01 04:34 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-10-01 06:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-01 12:03 UTC

   This incident has been resolved now.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Engage (US), Streaming Destinations (EU), Engage (EU), Profiles Sync, Journeys (US), Journeys (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 19:40 UTC

   We are currently investigating an issue causing formatting anomalies with S3 action destinations. Our team is working on a mitigation.

2. resolved 2026-09-16 21:50 UTC

   We have resolved the issue now.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-10 14:28 UTC

   We are actively investigating an issue in which some customers are unable to login to the Segment app via SSO.

2. identified 2026-09-10 15:27 UTC

   The root cause of the issue with SSO login has been identified and we are working on a fix.

3. resolved 2026-09-10 15:39 UTC

   The issue has been mitigated, and SSO login is now fully functional for the Segment app.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Engage (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-03 17:53 UTC

   We have identified an issue affecting the page load of Engage UI including Audiences and Journeys.

2. identified 2026-09-03 18:06 UTC

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

3. identified 2026-09-03 18:30 UTC

   We are continuing to take urgent action to fix this issue.

4. identified 2026-09-03 18:56 UTC

   We are continuing to take urgent action to fix this issue.

5. identified 2026-09-03 19:34 UTC

   We are continuing to take urgent action to fix this issue.

6. monitoring 2026-09-03 20:26 UTC

   A fix has been applied and the Engage UI experience should be fully functional. We are continuing to monitor results.

7. resolved 2026-09-03 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Web Interface (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-09-03 01:04 UTC

   We have identified an issue that may cause profile traits with no activity in the last 60 days to be unavailable in Audience Builder, trait and event pickers, and related trait detail views for some customers. This is a display issue only; underlying customer event and profile...

2. identified 2026-09-03 07:01 UTC

   We are continuing efforts to mitigate this issue.

3. identified 2026-09-03 14:05 UTC

   We are continuing efforts to mitigate this issue.

4. monitoring 2026-09-03 20:20 UTC

   A fix has been applied and the Engage UI experience should be fully functional. We are continuing to monitor results.

5. resolved 2026-09-03 22:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Web Interface (EU)

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-18 17:49 UTC

   We have identified an issue that is affecting a subset of Segment customers causing intermittent errors when logging in.

2. monitoring 2026-08-18 18:38 UTC

   Segment application login is now operating normally. We will continue to monitor for system stability.

3. resolved 2026-08-18 22:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 15:19 UTC

   We are currently deploying the fix to mitigate the issue

2. monitoring 2026-08-06 17:02 UTC

   This incident is resolved now

3. resolved 2026-08-07 06:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-06 05:50 UTC

   We are currently investigating an issue where security code verification notifications may not be delivered via email.

2. monitoring 2026-08-06 07:21 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-06 17:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Engage (US), Data Processing Pipeline (US), Journeys (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-07-26 01:43 UTC

   We have identified an issue impacting data processing affecting multiple components.

2. monitoring 2026-07-26 03:02 UTC

   A fix has been implemented, and we are actively monitoring the results.

3. resolved 2026-07-26 04:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-25 22:45 UTC

   We are currently investigating this issue.

2. identified 2026-07-25 23:29 UTC

   The issue has been identified and we are actively working on mitigation.

3. monitoring 2026-07-25 23:39 UTC

   A fix has been implemented, and we are actively monitoring the situation as processing latency recovers.

4. monitoring 2026-07-26 04:14 UTC

   Destination delivery is expected to recover in 30-40 minutes

5. resolved 2026-07-26 04:39 UTC

   This incident is now recovered.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-15 16:48 UTC

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

2. identified 2026-07-15 17:03 UTC

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

3. monitoring 2026-07-15 17:55 UTC

   Systems are recovering, we're actively monitoring.

4. resolved 2026-07-15 18:03 UTC

   This incident has been resolved

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-03 09:39 UTC

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

2. monitoring 2026-07-03 09:46 UTC

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

3. resolved 2026-07-03 10:43 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Warehouse Destinations (US), Linked Audiences (US), Reverse ETL (US), Linked Events (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-22 22:14 UTC

   An ongoing upstream outage with Snowflake is causing degraded performance for Segment products that rely on customer data warehouses. - Impacted Products: Linked Audiences, Linked Events, Reverse ETL, and Profile Sync. - Current Status: Syncs and data processing may be failing....

2. resolved 2026-06-23 00:22 UTC

   Snowflake outage has resolved and consequently impacted functionalities across segment have recovered as well.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-05 08:11 UTC

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

2. identified 2026-06-05 08:13 UTC

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

3. monitoring 2026-06-08 19:35 UTC

   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.

4. resolved 2026-07-03 09:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2026-05-08 01:59 UTC

   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.

2. monitoring 2026-05-08 03:58 UTC

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

3. resolved 2026-05-08 05:24 UTC

   Reddit Conversions API destination is operational.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-29 14:49 UTC

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

2. identified 2026-04-29 15:53 UTC

   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.

3. monitoring 2026-04-29 16:58 UTC

   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.

4. resolved 2026-04-29 19:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-04-27 22:00 UTC

   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.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-04-27 17:00 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Web Interface (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-13 19:02 UTC

   We are currently investigating an issue where the Audience Previews are not loading for some customers.

2. investigating 2026-04-13 19:04 UTC

   We are continuing to investigate this issue.

3. resolved 2026-04-13 19:19 UTC

   The issue impacting Audience Preview functionality has been resolved. Audience Preview is now operating normally.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Reverse ETL (EU), Reverse ETL (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-09 16:40 UTC

   Certain Reverse ETL syncs are experiencing failures. The team is currently investigating the issue.

2. identified 2026-04-09 18:15 UTC

   We've identified the issue and are currently working on mitigating it.

3. monitoring 2026-04-09 19:29 UTC

   A fix has been implemented and Reverse ETL syncs are now proceeding successfully without any failures. We are closely monitoring the recovery process.

4. resolved 2026-04-09 19:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 17:07 UTC

   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.

2. identified 2026-04-07 17:10 UTC

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

3. monitoring 2026-04-07 17:37 UTC

   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.

4. resolved 2026-04-07 18:30 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-03-31 16:30 UTC

   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.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US)

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-03-19 19:33 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...

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (EU)

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-17 18:55 UTC

   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.

2. resolved 2026-03-17 19:39 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Public API (US), Web Interface (EU), Public API (EU)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-09 14:40 UTC

   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.

2. identified 2026-03-09 17:18 UTC

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

3. identified 2026-03-09 20:51 UTC

   The engineering team is still working on mitigating the issue.

4. identified 2026-03-09 22:29 UTC

   The issue has been mitigated.

5. resolved 2026-03-10 00:45 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Cloud Sources (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2026-02-26 05:51 UTC

   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

2. resolved 2026-02-26 06:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Analytics.js CDN (US), Analytics.js CDN (EU)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-02-06 21:58 UTC

   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.

2. monitoring 2026-02-07 00:30 UTC

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

3. resolved 2026-02-07 07:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-27 17:17 UTC

   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.

2. resolved 2026-01-27 19:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-25 11:37 UTC

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

2. identified 2026-01-25 17:01 UTC

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

3. monitoring 2026-01-26 08:10 UTC

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

4. resolved 2026-01-26 09:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-26 19:00 UTC

   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.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 13:33 UTC

   We are observing elevated ETIMEDOUT errors from Yahoo DSP destination. We are currently investigating the issue.

2. identified 2026-01-22 14:36 UTC

   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.

3. monitoring 2026-01-22 16:02 UTC

   The incident has been mitigated and we are monitoring the destination. We will provide updates as more information becomes available from Yahoo team.

4. resolved 2026-01-22 17:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-09 20:39 UTC

   We are currently investigating the issue.

2. monitoring 2026-01-09 21:02 UTC

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

3. resolved 2026-01-09 21:18 UTC

   The issue has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Warehouse Destinations (US), Reverse ETL (EU), Linked Events (EU), Linked Audiences (US), Warehouse Destinations (EU), Reverse ETL (US), Linked Events (US), Linked Audiences (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-12-16 06:37 UTC

   We are currently monitoring the issue . Outage is declared here : https://status.snowflake.com/incidents/xdxj4klf7sc5

2. investigating 2025-12-16 08:24 UTC

   We are continuing to investigate this issue.

3. resolved 2025-12-16 16:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Data Processing Pipeline (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-12-09 22:11 UTC

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

2. monitoring 2025-12-09 23:42 UTC

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

3. resolved 2025-12-10 02:28 UTC

   Event delivery has returned to normal.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-24 01:47 UTC

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

2. identified 2025-11-24 03:20 UTC

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

3. monitoring 2025-11-24 03:53 UTC

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

4. monitoring 2025-11-24 04:50 UTC

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

5. monitoring 2025-11-24 04:50 UTC

   We are continuing to monitor for any further issues.

6. resolved 2025-11-24 05:04 UTC

   We've confirmed that the impacted destinations have recovered.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-11-21 00:38 UTC

   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.

2. resolved 2025-11-21 01:21 UTC

   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.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-11 01:04 UTC

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

2. identified 2025-11-11 01:45 UTC

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

3. monitoring 2025-11-11 03:32 UTC

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

4. resolved 2025-11-11 03:49 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Reverse ETL (EU), Reverse ETL (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-11-04 01:09 UTC

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

2. identified 2025-11-04 04:32 UTC

   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.

3. identified 2025-11-04 15:51 UTC

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

4. resolved 2025-11-04 17:56 UTC

   We've restored the ReverseETL delivery counts in the US

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Cloud Sources (US), Cloud Sources (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-10-20 10:11 UTC

   Segment is observing service unavailable error from intercom APIs.

2. monitoring 2025-10-20 12:00 UTC

   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.

3. monitoring 2025-10-20 13:52 UTC

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

4. resolved 2025-10-21 00:31 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Engage (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-14 20:46 UTC

   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.

2. monitoring 2025-10-14 21:38 UTC

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

3. resolved 2025-10-14 22:18 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-09 17:09 UTC

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

2. monitoring 2025-10-09 17:41 UTC

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

3. resolved 2025-10-09 18:21 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Data Ingestion (Tracking) API (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-10-05 23:24 UTC

   We are currently investigating this issue.

2. resolved 2025-10-05 23:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-10-02 13:35 UTC

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

2. monitoring 2025-10-02 14:27 UTC

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

3. resolved 2025-10-02 15:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Web Interface (US), Engage (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-25 15:40 UTC

   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.

2. identified 2025-09-25 16:56 UTC

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

3. identified 2025-09-25 21:02 UTC

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

4. monitoring 2025-09-26 14:24 UTC

   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.

5. resolved 2025-09-28 13:32 UTC

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

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Cloud Sources (US), Cloud Sources (EU)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-24 03:48 UTC

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

2. identified 2025-09-24 04:12 UTC

   The issue has been identified and a fix is being implemented

3. identified 2025-09-24 04:13 UTC

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

4. monitoring 2025-09-24 04:31 UTC

   A fix has been implemented and we are monitoring the results

5. resolved 2025-09-24 06:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-19 03:59 UTC

   We are currently investigating this issue.

2. investigating 2025-09-19 06:46 UTC

   We are continuing to investigate this issue.

3. identified 2025-09-19 07:48 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-09-19 08:20 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-09-19 10:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Streaming Destinations (US), Streaming Destinations (EU)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-17 21:37 UTC

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

2. identified 2025-09-17 21:58 UTC

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

3. monitoring 2025-09-17 22:18 UTC

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

4. monitoring 2025-09-17 23:08 UTC

   We are continuing to monitor for any further issues.

5. resolved 2025-09-18 01:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Segment's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-09-09 14:23 UTC

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

2. resolved 2025-09-09 21:42 UTC

   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.

Excerpts are shortened. Read the full incident on Segment's status page.

Affected: Reverse ETL (US)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-15 04:36 UTC

   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.

2. monitoring 2025-08-15 04:44 UTC

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

3. resolved 2025-08-15 06:26 UTC

   The incident is now fully resolved.

Excerpts are shortened. Read the full incident on Segment's status page.