Segment: Elevated Profile API Latencies
AWS outage, Dec 15, 2021 · 23 vendors, 27 incidents
Segment’s incident depends on AWS (declared dependency, named as a cause before); it did not name AWS. (hop 1, posted +1 h 35 min vs the first vendor naming AWS)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["AWS<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>15 vendors, 11 blamed AWS<br/>Daily, Gusto, Logz.io, Firebolt +11"]:::blames
root --> h1
dr["Known dependency<br/>6 vendors<br/>Plivo, Sinch, Bandwidth, Teleport +2"]:::hop2
root -.->|"depends on AWS"| dr
me["Segment (this incident)<br/>posted +1 h 35 min"]:::me
root -.->|"known dependency"| meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
This incident has been resolved, Profile API latencies have returned to normal levels
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 2021-12-15 17:07 UTC, resolved after 52 min, 1 update(s).
- Title
- Elevated Profile API Latencies
- Vendor
- Segment
- Date
- URL
- https://rewindex.com/company/segment/incidents/f19444plj5sv
Segment profileRecent Segment incidentsAll outages on December 15, 2021Segment in December 2021MarkdownJSON