Loading status…
Intercom status · Communication · checked (47s ago)
Also searched as Fin, Fin AI, Intercom Messenger.
No — Intercom is not down. All Intercom systems are reported operational.
According to Intercom's official status page, Intercom was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Intercom's feed reported no outage in 99.93% of our checks.
Everything above is read from Intercom's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Intercom in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Intercom is customer messaging and support — the chat widget on a website, a shared inbox, help centre articles and, increasingly, the Fin AI agent that answers tickets automatically. Intercom now publishes its status under the Fin brand.
The status page separates the messenger that loads on your website from the agent-facing inbox and from the API and Fin itself. The messenger is the component your customers see: it can fail to load on your site while your support team's inbox works normally, and that failure is invisible from inside Intercom.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Intercom's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Intercom was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 47s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Intercom's status endpoint.
Intercom has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Intercom posted itself — not every problem users hit.
resolved · Sep 16, 11:51 AM (3d ago)
resolved · Sep 9, 03:55 PM (10d ago)
resolved · Sep 4, 03:16 PM (15d ago)
resolved · Sep 3, 02:29 PM (16d ago)
resolved · Aug 26, 02:26 PM (24d ago)
resolved · Aug 19, 11:12 PM (31d ago)
resolved · Aug 3, 02:22 PM (47d ago)
resolved · Jul 15, 03:21 PM (66d ago)
resolved · Jul 10, 04:57 AM (72d ago)
resolved · Jun 24, 11:03 AM (87d ago)
resolved · Jun 23, 05:55 PM (88d ago)
resolved · Jun 12, 02:30 PM (99d ago)
resolved · Jun 11, 09:54 AM (100d ago)
resolved · Jun 10, 01:19 PM (101d ago)
resolved · Jun 1, 11:03 AM (110d ago)
resolved · May 21, 11:09 AM (121d ago)
resolved · May 20, 10:16 AM (122d ago)
resolved · Apr 30, 04:58 PM (142d ago)
resolved · Apr 27, 11:43 AM (145d ago)
resolved · Apr 21, 11:30 PM (151d ago)
The messenger is a third-party script, so ad blockers and content security policies stop it loading for a share of real visitors with nothing wrong at Intercom. Conversations not routing is usually an assignment rule rather than an incident. Fin answering badly is a content and training problem, and no status page reports on answer quality.
