Intercom and its Fin assistant went down for customers hosted in the US region starting at 19:15 UTC on 16 November 2026. The fault sits on Intercom's side, and as of the last update it was still open with no resolution posted.
Started
19:15 UTC
Duration
Ongoing
Source
IsDown
Next time
Intercom is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
What happened?
Intercom's own status page opened an incident titled "Intercom is down" at 19:15 UTC. The first update said Intercom and Fin were experiencing difficulties and that the team was investigating. Three minutes later, at 19:18 UTC, Intercom narrowed the scope, saying the outage was primarily affecting customers hosted in the US region, with other regions appearing unaffected. That second update is the last one on record, so the incident is still open with no cause given and no fix announced. Intercom has not published a post-mortem, and no component list was attached to this incident, so there is no breakdown of which specific services (inbox, messenger, Fin) were hit beyond the general statement. No user reports were filed in this window on our end, which is not unusual for a fast-moving, regionally scoped incident. Over the past 90 days, Intercom has logged 10 incidents with a median duration of 27 minutes, and over its lifetime it averages 4.6 incidents a month across 357 total incidents. This one, still ongoing at the time of the last Intercom update, has already outlasted that 90 day median. With only two updates and a narrow scope statement, there isn't much more detail to go on than what Intercom itself chose to publish.
Learning
Our own 30 day monitoring of Intercom shows 3 incidents, with 2 resolved and a median duration of 10h 54m, numbers that come from checking Intercom's endpoints from outside, not from reading Intercom's internal status page. An external check and a vendor-reported outage can both be true at once: your monitoring might show Intercom's public endpoint responding fine while a backend dependency like Fin or a specific regional cluster is degraded, which is exactly the shape of this incident, scoped to the US region while other regions were reported as unaffected. This is a case where the failure sits inside Intercom's infrastructure, in a layer you cannot see or probe from your own product, so watching your own endpoints would tell you your integration is calling out correctly but nothing about whether Intercom can actually process what you send. When a vendor narrows an outage to one region partway through, it's a signal the fault is more specific than the first alert suggested, and that detail matters if your users are concentrated in that region. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.