Segment: Partial Sync Failures for Profiles Sync
Timeline of updates
- identified
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. - resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
17b502cef6fb047a…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Segment, started 2025-09-09 14:23 UTC, resolved after 7.3 h, 2 update(s).
- Title
- Partial Sync Failures for Profiles Sync
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/l3fn7k0dsgmx
Segment profileRecent Segment incidentsAll outages on September 9, 2025Segment in September 2025MarkdownJSON