Is Segment Down Right Now? Check if there is a current outage ongoing.

We've identified an incident affecting batch computations, broadcasts, backfills, CSV downloads, audience previews, and prediction jobs. Our engineering teams are actively investigating and working on a resolution.

We are investigating an issue with destination delivery delay. This appears due to downstream outages in various cloud providers.

We are experiencing increased event data processing delay in Engage and are actively investigating.

This incident has been resolved.

Our engineering teams are actively investigating the root cause and working to restore full functionality. We will provide updates as more information becomes available.

We are currently investigating this issue.

Our engineering teams are actively investigating the root cause and working to restore full functionality. We will provide updates as more information becomes available.

We are currently investigating this issue.

This incident has been resolved.

There may be periods of delay when requesting a security code (for email login or generating a token) or other alerting notifications. Notifications are eventually delivered (spikes of 15 minute delay). There is no impact on event delivery.

There may be periods of delay when requesting a security code (for email login or generating a token) or other alerting notifications. Notifications are eventually delivered (spikes of 15 minute delay). There is no impact on event delivery.

This incident has been resolved

We are fully back live.

We are currently investigating an issue with the Segment web application and public API.

We are currently investigating an issue with the Segment web application and public API.

This incident has been resolved.

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

We are investigating an issue with the Audience UX not loading for realtime audiences. There is no impact to data delivery.

We are investigating an issue with the Audience UX not loading for realtime audiences. There is no impact to data delivery.

All new model scores have been successfully generated. The Predictions Overview page will automatically update as additional data becomes available for the new predictions. We appreciate your patience as the updated results are reflected.

We have deployed a fix, and the correct model scores are now being generated. Please note that the conversion history on the Predictions Overview page may still display incorrect results; we are actively working to resolve this issue.

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

We've identified a bug that is affecting the accuracy of scores for certain predictive traits. This issue may temporarily reduce the performance of those scores. Our engineering team is actively working on a fix and we will provide further updates as progress is made.

This incident has been resolved.

Processing delay is recovering and we are continuing to monitor closely.

We detected an issue that affected identity resolution and profile data update may be delayed. We have deployed a change to address the issue and are closely monitoring.

We detected an issue that affected identity resolution and profile data update may be delayed. We have deployed a change to address the issue and are closely monitoring.

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

We've identified a bug that is affecting the accuracy of scores for certain predictive traits. This issue may temporarily reduce the performance of those scores. Our engineering team is actively working on a fix and we will provide further updates as progress is made.

This incident has been resolved.

We are currently monitoring potential impact due to the current Snowflake incident. https://status.snowflake.com/incidents/9mwvw50z4wnm For customers using Snowflake in the impacted regions, they may see failed warehouse syncs in Reverse ETL, Linked Audiences, Linked Events, Profile Sync, and Snowflake Destination. These will be retried in the next scheduled sync. More details available in Snowflake incident. For any questions, please reach out to the Segment support team.

Between 6:18am ET and 8:28am ET we experienced delays of up to 1h 42m processing messages for some Engage Audiences, Computed Traits, and Journeys. No data has been lost, and the system has fully recovered. Some audience and journey conditions using time windows of 1 hour or less may not have output values during this incident.

Lag has fully recovered.

We've mitigated the issue and we're monitoring the recovery.

We've identified an issue causing a small portion of EU connections traffic to lag behind up to an hour.

This incident has been resolved.

As we investigate a technical issue, Delivery Samples in Event Delivery, Delivery Overview and in Failed RETL syncs are temporarily unavailable.

This incident has been resolved.

As we investigate an issue, Delivery Samples in Event Delivery and Delivery Overview are unavailable.

This incident has been resolved.

We have identified an issue with Warehouse Destinations that affects US workspace customers. Data delivery is delayed. A fix has been implemented and we are monitoring the result.

The delay in the identity resolution pipeline has been resolved.

Fix is deployed. We are seeing improvements and will continue to monitor the recovery.

We have identified the case for the issue and are working on a fix.

We have detected in an increase in delay in identity resolution and are actively investigating.

This incident is now resolved, and Audiences, Journeys and Computed Traits are processing data as expected.

We are continuing to monitor the recovery process and estimate that we will be fully back to real-time within the next 30 minutes.

We are continuing to monitor the recovery process and estimate that we will be fully back to real-time within 4 hours.

We're currently experiencing delays of up to 7 hours processing messages for some Engage Audiences, Computed Traits, and Journeys. The issue has been identified and the recovery process has started. No data has been lost. Some audience and journey conditions using time windows of 7 hours or less may not have output values during this incident.

This incident has been resolved.

Generative Audiences, Suggested Mappings, and Functions Writer and Analyzer are currently unavailable due to an AI vendor outage.

The missing links have been fully recovered. Batch computations and Predictions will automatically include the updates in the subsequent runs. There has been no impact to the Profile API and real-time computations. We apologize for the inconvenience.

We identified and resolved an issue where a small percentage of profiles lost links post-merge, affecting event attribution to canonical profiles. There is no data loss. We are working to recover the missing links for accurate profile and computations updates.

The issue has been identified.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved

We are currently investigating this issue.

On Nov 11, from 6:38AM UTC to Nov 13 12:45PM UTC, customers may have experienced an issue where their users were unable to get custom identifiers added to their profiles. Our engineers have identified and deployed a fix. We apologize for any inconvenience this may have caused.

The issue has now been resolved and Syncs to amazon-kinesis-firehose, amazon-personalize, amazon-lambda and amazon-eventbridge are now flowing.

We have also now recovered AWS Lambda. We will continue working through and monitoring the issue.

amazon-kinesis-firehose and amazon-eventbridge have recovered - we will continue monitoring while working to recover amazon-lambda

We have identified an issue with Syncs to amazon-kinesis-firehose, amazon-personalize, amazon-lambda and amazon-eventbridge and working to resolve.

We have successfully mitigated the issue and are fully back to real-time processing.

We are continuing to monitor the recovery process and estimate that we will be fully back to real-time within 1 hour.

We're currently experiencing delays of up to 4 hours processing messages for 53.67% of Engage Audiences, Computed Traits, and Journeys. The issue has been identified and the recovery process has started. We estimate 38% of the affected computations will be back to real-time in the next 30 minutes, and the remainder will be back to real-time within 3 hours. No data has been lost.

Maintenance complete.

We will be conducting scheduled maintenance on our core configuration management database. During this period, the App and Public API will be read-only and login functionality will not be working.

We identified and resolved an isolated event delivery delay in our EU environment that caused delays for 10% of connections traffic up to 40 minutes.

This incident has been resolved.

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

We have identified an issue with Data Lakes that affects some customers. Syncs to Data Lakes are taking longer than expected. No data loss has occurred.

This incident has been resolved.

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

We are currently experiencing a high error rate with Engage batch computations.

This incident has been resolved.

A fix has been implemented and we are monitoring results.

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

We are currently investigating this issue.

This incident has been resolved.

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

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

We are currently investigating the issue.

This incident has been resolved.

We have identified an issue and deployed a fix. Profiles API in EU is recovering.

We detected increased error rate in Profile API for our EU region service and are actively investigating.

This incident has been resolved.

We detected a an issue that's causing a delay in data processing in Engage. A fix has been deployed and we are monitoring closely.

Delivery delays to Amazon Kinesis of over an hour due to AWS outage.

This incident has been resolved.

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

We are investigating an issue with Databricks ReverseETL and Destination that is affecting all customers.

All systems have recovered. We have resolved this incident

We identified the root cause and fixed the issue. Our systems are recovering. We continue to monitor the recovery

We have an incident impacting many products in the EU. We are investigating this. Multiple products such as Engage, rETL, Profile Sync are impacted in the EU. At this time the scope of impact is a delay in the impacted services.

Heap.io confirmed that the AWS outage affecting data delivery operation is now resolved.

Our partner Heap.io is having an outage. We are monitoring the situation. For heap specific information visit https://www.heap.io/status

A fix has been implemented, and we are continuing to monitor the result.

The Segment engineering team has acknowledged an incident affecting customers with Engage Premier. These customers are currently unable to create new email templates or edit existing ones. When attempting to do so, an error message stating "Something went wrong" appears. We are actively working on resolving this issue and will provide updates as soon as possible. Thank you for your patience.

This incident has been resolved.

We have identified a root cause and are working to mitigate the issue.

The connectivity to Intercom fetching "Conversations" collection is restored.

Segment is seeing timeout errors when calling Intercom "Conversations" collection API endpoint. We started the investigation by reaching out to Intercom for assistance.

The connectivity to Clearbit destination is now fully recovered.

We are currently investigating the issue. The API endpoint at Clearbit is returning unexpected errors.

Recovery from delivery latency is now fully resolved.

Event delivery for streaming connections is delayed, roughly 50% of connections are currently experiencing up to 30 minutes of delivery delay.

This incident has been resolved.

We have routed new traffic away from the degraded infrastructure, but events received in the past hour may see elevated latency.

This incident has been resolved.

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

We are experiencing delay in processing data onto Unify profiles and Twilio Engage (US). Engineering team has identified and mitigating an underlying issue.

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 the delayed syncs and incorrect counts. No data has been lost.

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

We have identified the issue causing the delay and currently working on fixing it.

As of 12:00 PM UTC on 11.03.2024, our Segment Data Collection Activation -Streaming Sources service was impacted for 2 hours. Support team has received reports that EU customers were not receiving events in their sources since roughly 12:00pm UTC. A traffic surge caused this incident. Platform has finished processing through the surge. There is no data loss. The impact was a 2 hour delay for EU traffic. EU Systems are back to normal. The team continues to monitor it.

This incident has been resolved.

This incident has been resolved.

We have identified the issue and implemented a fix. Processing has resumed and we are monitoring recovery.

We're currently experiencing delays processing Engage Audiences, Computed Traits, and Journeys created between Aug 8th 2022 and Aug 19th 2022, as well as those created between Aug 22 2022 and March 14th 2023. Our engineers are working on identifying a solution. No data has been lost.

This Workspace access issue is now resolved, and there was no data loss as a result of this incident. Thank you again for your patience while we worked through this.

A fix has been deployed, and workspace access has now resumed. We are monitoring the situation for stability before resolving. Thank you for your patience.

We are continuing to make progress on the root cause of the errors. Workspace access is improving, with occasional errors experienced. We will continue to provide updates as more information becomes available. Thank you for your patience.

We are making progress on restoring access to workspaces and resolving the API errors. We will continue to provide updates as more information becomes available. Thank you for your patience.

We are actively working to restore access to workspaces and resolve the API errors. Please note, there is no impact on data ingestion or delivery to destinations.

Customers attempting to access their workspaces within the web app on US and EU are met with an error message. We're investigating the issue and will post updates as soon as we have further information.

We experienced an intermittent issue while ingesting data into Snowflake destination which caused sync delays for a small subset of customers. The issue is now resolved with no data loss reported.

This incident has been resolved

A fix has been implemented and we are monitoring the results

The issue has been identified and a fix is being implemented

We are currently investigating an issue affecting Source API Keys page, which is not loading due to an error

This issue is resolved. Audiences, Computed Traits, and Journeys are now all processing in real-time.

We have identified the issue and implemented a fix. Processing has resumed and we are monitoring recovery.

We're currently experiencing delays processing Engage Audiences, Computed Traits, and Journeys created before February 2021, between May 19 2022 and July 18th 2022, and between July 13 2023 and July 19 2023. Our engineers are working on identifying a solution. No data has been lost.

This incident has been resolved.

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

We are investigating an issue with the Segment web interface and public api that is affecting all customers. Data ingestion is not affected.

We experienced an delay processing data onto Unify profiles and into Twilio Engage (US). Engineering team has identified and mitigated an underlying issue. Data processing delay recovered after 4.5 hours.

This incident has been resolved

A fix has been implemented and we are monitoring the results

The team has identified the issue and a fix is being implemented. We will provide an update you soon.

We are currently investigating an issue affect the Segment Search functionality. Our team is working on identifying a fix and we will update this status as soon as we have more information.

Issue has been identified and resolved.

The actions mapping UI is experiencing issues. We are currently investigating them.