Skip to main content
Intercom logo

Is Intercom Down?

No — Intercom is up

Reachable from all 8 checked regions

Average response time: 844ms

Last checked · checks run every 6 hours

Official status page: https://www.intercomstatus.com

Intercom uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
915ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 1 day measured so far. A dash means we have no measurement for that window.

30-day history

Jun 29: no data
Jun 30: no data
Jul 1: no data
Jul 2: no data
Jul 3: no data
Jul 4: no data
Jul 5: no data
Jul 6: no data
Jul 7: no data
Jul 8: no data
Jul 9: no data
Jul 10: no data
Jul 11: no data
Jul 12: no data
Jul 13: no data
Jul 14: no data
Jul 15: no data
Jul 16: no data
Jul 17: no data
Jul 18: no data
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: 100.00% uptime, 30 checks
Jun 29 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
693ms
DNS 0ms TCP 0ms TLS 3ms TTFB 320ms
gru
850ms
DNS 0ms TCP 10ms TLS 11ms TTFB 403ms
iad
291ms
DNS 0ms TCP 1ms TLS 3ms TTFB 224ms
jnb
1428ms
DNS 0ms TCP 0ms TLS 2ms TTFB 742ms
lax
528ms
DNS 0ms TCP 2ms TLS 4ms TTFB 328ms
lhr
645ms
DNS 0ms TCP 7ms TLS 12ms TTFB 415ms
nrt
1415ms
DNS 0ms TCP 1ms TLS 5ms TTFB 341ms
ord
349ms
DNS 0ms TCP 1ms TLS 5ms TTFB 301ms
sin
1252ms
DNS 120ms TCP 0ms TLS 3ms TTFB 554ms

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 all 18 regions to find out where it breaks.

Test it yourself

Related services

Zendesk
Zendesk
HubSpot
HubSpot
Salesforce
Salesforce
Slack
Slack

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 — 8 of them answered the most recent check.
  • 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. We only change the 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 let it override us in both directions.

Get alerted when Intercom goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required