rewindex

CompaniesSegmentIncidents

Segment: Warehouse syncs not starting

No impact listedStatus: resolvedStarted Resolved (18 h)1 updatestatus.segment.com (opens in new tab)

Timeline of updates

  1. resolved

    We have confirmed that we have fully recovered and expect no further issues. Warehouse and source syncs will now start and complete correctly for all customers. No data was dropped during the extended outage and subsequent sync delays. If you see any problems, please don't hesitate to contact us at http://segment.com/help/contact (opens in new tab) This extended outage was caused by a series of cascading failures in our upstream infrastructure provider that was initially triggered by a scaling event on our end. We're actively working closely with them on diagnosing and resolving the underlying performance issue on their end as well as improving our ability to recover more quickly in situations similar to this.

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: none) posted by Segment, started 2017-12-07 01:00 UTC, resolved after 18 h, 1 update(s).

Title
Warehouse syncs not starting
Vendor
Segment
Date
URL
https://rewindex.com/company/segment/incidents/0x7gxx8tvn4x

Segment profileRecent Segment incidentsAll outages on December 7, 2017Segment in December 2017MarkdownJSON