Segment: Tracking API Failures

MinorStatus: resolvedStarted 2017-02-01 04:13 UTCResolved 2017-02-01 04:13 UTC (0 min)1 updatestatus.segment.com

Timeline of updates

resolved2017-02-01 04:13 UTC
On January 31st, 2017, from 5:30 PM to 6:30 PM PST, we experienced communication issues between our frontend load balancers and our Tracking API which resulted in a 0.8% loss of events sent from analytics.js.

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 2017-02-01 04:13 UTC, resolved after 0 min, 1 update(s).

Title: Tracking API Failures
Vendor: Segment
Date: 2017-02-01 04:13 UTC
URL: https://rewindex.com/company/segment/incidents/6h9pyymz6jnm

Segment profile Recent Segment incidents All outages on February 1, 2017 Segment in February 2017 Markdown JSON