Is Intercom Down?

No — Intercom is up

Intercom's status page: Not available · we could not read it
FlareWarden checks: Website reachable · 8 of 8 regions · 1077 ms

Right now

We could not read Intercom's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

intercom.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 1077 ms
Checked: 5 hours ago

By region

Chicago reachable, 523 ms
Johannesburg reachable, 1221 ms
London reachable, 833 ms
Los Angeles reachable, 706 ms
San Jose reachable, 620 ms
Singapore reachable, 1669 ms
Sydney reachable, 1673 ms
Tokyo reachable, 1376 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	182 ms	1 ms	3 ms	470 ms
Johannesburg	199 ms	1 ms	5 ms	985 ms
London	41 ms	5 ms	5 ms	448 ms
Los Angeles	83 ms	3 ms	5 ms	417 ms
San Jose	73 ms	3 ms	6 ms	366 ms
Singapore	143 ms	1 ms	3 ms	589 ms
Sydney	141 ms	1 ms	3 ms	602 ms
Tokyo	36 ms	2 ms	4 ms	657 ms

We check that intercom.com loads, not every feature behind it. Test it yourself

History

Intercom website availability

Measured by FlareWarden · intercom.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 975ms

Last 30 days

91-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of intercom.com from multiple regions every 6 hours. Intercom's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Intercom does

Intercom is a customer messaging platform combining an in-product chat messenger, a shared inbox for support teams and its Fin AI agent. Companies embed the messenger directly inside their own applications, so an Intercom outage removes the support channel from the product at the moment customers are most likely to reach for it.

What an outage looks like

The messenger fails to load in your product, usually showing as a missing launcher rather than an error, so customers see nothing at all and get no hint that anything failed. Agents cannot open the inbox or send replies, and conversations already open stop updating. Outbound messages and automated workflows may not fire on schedule.

What to do about it

Check the status page at finstatus.com and select your hosting region: Intercom reports US, EU and Australia separately, and yours is identifiable from your application URL (app.intercom.com, app.eu.intercom.com or app.au.intercom.com). Point customers at email while the launcher is missing, because a messenger that fails to render gives them no way to know their message went nowhere.

Is it down for everyone, or just you?

If this page says Intercom is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Intercom outage FAQ

Is Intercom down or is the messenger just not loading on my site?

Check finstatus.com for your region first. If Intercom is healthy, the usual local causes are a content security policy blocking the script, an ad blocker, or a recent change to how the snippet is installed. A genuine outage also affects the agent inbox, so ask a colleague whether they can open conversations before debugging your own site.

Why does Intercom report status by region?

Intercom hosts customers in the United States, Europe and Australia on separate infrastructure, and incidents frequently affect one region only. Your region is visible in the URL you log in at: app.intercom.com, app.eu.intercom.com or app.au.intercom.com. Reading the wrong region's status is the most common way to reach the wrong conclusion about an incident.

Do customer messages get lost during an Intercom outage?

Messages that reach Intercom are held and appear in the inbox once it recovers. The genuine loss is on the other side: if the messenger never rendered, the customer had no way to send anything, and there is no record of an attempt. That silent failure, rather than lost data, is the reason to publish an alternative contact route.

Does an Intercom outage affect Fin, the AI agent?

Fin answers through the same messenger, so if the messenger cannot load, Fin cannot reach the customer either. The status page is published under the Fin name and covers the platform as a whole per region. Conversations Fin was mid-way through resume once the region recovers rather than restarting from the beginning.

What should support teams do while the inbox is unavailable?

Move to whatever channel still works, usually email or a shared mailbox, and say so somewhere customers will see, such as a banner on your site or a pinned social post. Avoid bulk-replying the moment the inbox returns: conversations queued during the incident arrive together, and duplicate replies are easy to send in the rush.

How we measure this

We request Intercom's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Intercom publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Intercom itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when Intercom goes down

We check Intercom every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required