RewindexOutage eventsJan 9, 2026
Intercom outage, Jan 9, 2026
6 vendors posted 6 incidents between 20:00 and 21:00 UTC, against about 3 incidents from 3 vendors in the same hours on an ordinary week. 3 vendors named Intercom in 3 incidents (3 of them blamed it). Vendors reported an Intercom outage; Intercom’s own incident for this date is not in the archive.
Observed, not verified. A line means a vendor’s incident named another vendor, or started in the same window. It is not a proven cause.
Times are UTC; lags are from when the first vendor named Intercom.
- first vendor named Intercom 20:10
How it spread
Vendors that named Intercom, grouped by when they posted, and vendors that blamed one of the vendors Intercom took down. Solid lines: the vendor named the other. Dashed: same window, not named.
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 --> h1Vendors that named Intercom
In their own words. “Blames” means a causal phrase sits next to the name (“due to”, “upstream provider”…).
Within an hour
3 vendors
- Incident, no impact listed
+0 min
Blames Intercom
…Live Chat Interruption Our upstream provider, Intercom, is back online. Customers can now utilize live chat to reach out for support. Intercom has implemented a fix and we are monitoring the results.…
- Major incident
+23 min
Blames Intercom
Sigma ComputingChat Support experiencing 3rd party outage
…convenience this has caused, and appreciate your understanding. Our 3rd party chat system Intercom is currently experiencing an outage as listed here https://www.intercomstatus.com/us-hosting. If you…
- Minor incident
+29 min
Blames Intercom
SegmentWe are currently investigating the issue. The API endpoint at Intercom is returning timeout errors.
…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…
Same window, did not name anyone
3 incidents started during the event without naming Intercom or another vendor. Some are part of it, some are a normal day’s background (about 3 in these hours).
Show all 3
- −8 minCritical incident
- +36 minMajor incident
- +45 minMinor incident
Detected automatically from 9 status pages opening incidents in the peak hour (normally at most 8). Mentions are matched by name in each incident’s title and updates, then classified as cause, location or integration; quoted text is the vendor’s. Vendors that share one status page are shown once.