Segment: Warehouse syncs failing with "internal error"
Timeline of updates
- resolved
We've resolved the issue and all warehouse syncs are now starting successfully. This issue only affected warehouse syncs for object sources and no data was lost. All warehouses will catch up during their next regular sync. A cascading failure in an authentication mechanism in our objects pipeline caused these syncs to fail to start for all warehouses. To prevent this class of failure from occurring again we are removing unneeded components that caused this issue to take longer than necessary to resolve.
From Segment’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.segment.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Segment, started 2018-01-25 23:32 UTC, resolved after 2.0 h, 1 update(s).
- Title
- Warehouse syncs failing with "internal error"
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/1676fzffmhv2
Segment profileRecent Segment incidentsAll outages on January 25, 2018Segment in January 2018MarkdownJSON