Segment: Destinations Retries Degraded
Timeline of updates
- resolved
During a migration to new infrastructure underlying the Destinations product, we inadvertently degraded retry behavior. Since 9/25, all destinations (other than Google Analytics, Adwords, Webhooks, Mailchimp, S3, and Warehouses) haven't been retrying. Normally, we retry a failed request to a partner five times over the course of a few hours. Segment's data delivery has been at parity with the native API partner performance and hasn't been doing the retry logic. We have just fixed this and you'll see our standard retry logic moving forward.
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-10 05:09 UTC, resolved after 0 min, 1 update(s).
- Title
- Destinations Retries Degraded
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/40rqtzksj2d4
Segment profileRecent Segment incidentsAll outages on December 10, 2017Segment in December 2017MarkdownJSON