Segment: We are currently investigating the issue. The API endpoint at Intercom is returning timeout errors.
Intercom outage, Jan 9, 2026 · 6 vendors, 6 incidents
Segment’s incident blames Intercom as the cause. (hop 1, posted +29 min vs the first vendor naming Intercom)
“…We are currently investigating the issue. The API endpoint at Intercom is returning timeout errors. The issue has been resolved. The issue has been resolved. The partner has fixed the issue. We are ac…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Intercom<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>3 vendors, 3 blamed Intercom<br/>Lattice, Sigma Computing, Segment"]:::blames
root --> h1
me["Segment (this incident)<br/>posted +29 min"]:::me
h1 --- 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.
Affected components: Streaming Destinations - Streaming Destinations (US)Streaming Destinations (US)Streaming Destinations (EU)Streaming Destinations - Streaming Destinations (EU)
Timeline of updates
- investigating
We are currently investigating the issue.
- monitoring
The partner has fixed the issue. We are actively monitoring to see if the issue is completely resolved.
- resolved
The issue has been resolved.
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 18:22 UTC
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on Oct 19, 23:18 UTC. Record hash
2abb6dcf0fc97023…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).