Segment had 55 outages in the last 2 years totaling 37h 51m of downtime — averaging 2.3 incidents per month.
There were 55 Segment outages since May 28, 2025 totaling 37h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
Fix was implemented and rolled out. Impacted workflows are operating normally.
This incident has been resolved.
We are investigating an issue with destination delivery delay. This appears due to downstream outages in Google Cloud Services.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are seeing degradation across products leveraging GCP, including SQL Traits, rETL, LinkedAudiences, and Streaming, Storage, and BlobStore destinations. We are currently seeing no indication of data loss.
We are seeing that GCS based Global Storage Destinations have fully recovered. We continue to monitor impacted products for recovery.
All impacted Segment Products have recovered, and we will continue to monitor throughout the day. If you have questions or continued concerns with your implementation, please reach out via normal support channels.
This incident has been resolved.
We are experiencing increased event data processing delay in Engage and are actively investigating.
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 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.
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.
This incident has been resolved.