Segment: CDN elevated error rate
Timeline of updates
- resolved
We've been investigating alerts related to an increase in our CDN error rate. Between 2016-12-14T07:15 UTC and 2016-12-14T15:00 UTC we saw an increased error rate in mobile settings and Analytics.js responses. Between 1% and 6% of these requests responded with a 502 error and were unable to be served to the client. We've since fixed the problem with the faulty origin, and behavior has been restored to normal.
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 2016-12-14 15:21 UTC, resolved after 0 min, 1 update(s).
- Title
- CDN elevated error rate
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/ywl2rnpgysv0
Segment profileRecent Segment incidentsAll outages on December 14, 2016Segment in December 2016MarkdownJSON