Skip to content

Outage tracker / Intercom

Is Intercom down?

I'm having a problem

Vendor reports no incidentWhat Intercom reports

Intercom reports no incident on its status page.

As of the last successful poll, 2026-11-05 13:39 UTC.

Intercom's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 3 minutes ago

Our checks of Intercom pass from all 10 regions we check.

As of Nov 5, 2026, 2:00 PM UTC, RealUptime's checks of Intercom passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:00 PM UTC
US-East728 msChecks passing
US-West3136 msChecks passing
Europe1392 msChecks passing
Asia-Pacific2234 msChecks passing
US-Central416 msChecks passing
Canada884 msChecks passing
UK967 msChecks passing
Southeast Asia2364 msChecks passing
Australia2589 msChecks passing
South America1174 msChecks passing
their status pagetheir claim, not our reading

Intercom reports: All systems operational (“All Systems Operational”)

from Intercom's own status page, checked Nov 5, 2026, 1:05 PM UTC
Intercom's own status page shows no incident, and our checks of Intercom pass right now.

This is Intercom's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Intercom response time, by region

US-East
1.9sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 515ms2026-10-08 UTC: p95 640ms2026-10-09 UTC: p95 399ms2026-10-10 UTC: p95 466ms2026-10-11 UTC: p95 437ms2026-10-12 UTC: p95 565ms2026-10-13 UTC: p95 600ms2026-10-14 UTC: p95 552ms2026-10-15 UTC: p95 364ms2026-10-16 UTC: p95 507ms2026-10-17 UTC: p95 1.1s2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.4s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.4s2026-10-24 UTC: p95 1.3s2026-10-25 UTC: p95 1.4s2026-10-26 UTC: p95 1.8s2026-10-27 UTC: p95 1.3s2026-10-28 UTC: p95 1.2s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.3s2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
2.0sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 805ms2026-10-08 UTC: p95 814ms2026-10-09 UTC: p95 853ms2026-10-10 UTC: p95 745ms2026-10-11 UTC: p95 840ms2026-10-12 UTC: p95 750ms2026-10-13 UTC: p95 675ms2026-10-14 UTC: p95 780ms2026-10-15 UTC: p95 566ms2026-10-16 UTC: p95 629ms2026-10-17 UTC: p95 1.0s2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 1.5s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.9s2026-10-27 UTC: p95 1.6s2026-10-28 UTC: p95 1.5s2026-10-29 UTC: p95 1.5s2026-10-30 UTC: p95 1.6s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.5s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Europe
2.0sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 716ms2026-10-08 UTC: p95 764ms2026-10-09 UTC: p95 772ms2026-10-10 UTC: p95 709ms2026-10-11 UTC: p95 726ms2026-10-12 UTC: p95 719ms2026-10-13 UTC: p95 517ms2026-10-14 UTC: p95 728ms2026-10-15 UTC: p95 698ms2026-10-16 UTC: p95 522ms2026-10-17 UTC: p95 916ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 1.0s2026-10-20 UTC: p95 724ms2026-10-21 UTC: p95 852ms2026-10-22 UTC: p95 979ms2026-10-23 UTC: p95 838ms2026-10-24 UTC: p95 723ms2026-10-25 UTC: p95 778ms2026-10-26 UTC: p95 1.0s2026-10-27 UTC: p95 1s2026-10-28 UTC: p95 684ms2026-10-29 UTC: p95 755ms2026-10-30 UTC: p95 848ms2026-10-31 UTC: p95 869ms2026-11-01 UTC: p95 874ms2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
Asia-Pacific
2.8sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.1s2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 891ms2026-10-14 UTC: p95 954ms2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 1.8s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.0s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 2.0s2026-10-22 UTC: p95 2.2s2026-10-23 UTC: p95 2.2s2026-10-24 UTC: p95 2.0s2026-10-25 UTC: p95 1.9s2026-10-26 UTC: p95 2.8s2026-10-27 UTC: p95 2.1s2026-10-28 UTC: p95 2.0s2026-10-29 UTC: p95 2.1s2026-10-30 UTC: p95 2.0s2026-10-31 UTC: p95 3.3s2026-11-01 UTC: p95 3.3s2026-11-02 UTC: p95 3.2s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 2.8s
Oct 7Oct 21Nov 5
US-Central
1.0sp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 622ms2026-10-08 UTC: p95 460ms2026-10-09 UTC: p95 475ms2026-10-10 UTC: p95 397ms2026-10-11 UTC: p95 446ms2026-10-12 UTC: p95 488ms2026-10-13 UTC: p95 565ms2026-10-14 UTC: p95 585ms2026-10-15 UTC: p95 376ms2026-10-16 UTC: p95 478ms2026-10-17 UTC: p95 873ms2026-10-18 UTC: p95 1.0s2026-10-19 UTC: p95 984ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 1.3s2026-10-23 UTC: p95 1.2s2026-10-24 UTC: p95 879ms2026-10-25 UTC: p95 1.0s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 939ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 1.0s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 740ms2026-11-04 UTC: p95 720ms2026-11-05 UTC: p95 1.0s
Oct 7Oct 21Nov 5
Canada
1.2sp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 601ms2026-10-08 UTC: p95 527ms2026-10-09 UTC: p95 542ms2026-10-10 UTC: p95 567ms2026-10-11 UTC: p95 540ms2026-10-12 UTC: p95 486ms2026-10-13 UTC: p95 534ms2026-10-14 UTC: p95 581ms2026-10-15 UTC: p95 548ms2026-10-16 UTC: p95 521ms2026-10-17 UTC: p95 854ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.1s2026-10-20 UTC: p95 1.2s2026-10-21 UTC: p95 1.2s2026-10-22 UTC: p95 1.5s2026-10-23 UTC: p95 1.5s2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.5s2026-10-26 UTC: p95 1.7s2026-10-27 UTC: p95 1.5s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.3s2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.2s2026-11-03 UTC: p95 956ms2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.2s
Oct 7Oct 21Nov 5
UK
1.1sp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 437ms2026-10-08 UTC: p95 473ms2026-10-09 UTC: p95 526ms2026-10-10 UTC: p95 460ms2026-10-11 UTC: p95 466ms2026-10-12 UTC: p95 593ms2026-10-13 UTC: p95 446ms2026-10-14 UTC: p95 424ms2026-10-15 UTC: p95 345ms2026-10-16 UTC: p95 454ms2026-10-17 UTC: p95 862ms2026-10-18 UTC: p95 1.2s2026-10-19 UTC: p95 1.2s2026-10-20 UTC: p95 1.3s2026-10-21 UTC: p95 1.0s2026-10-22 UTC: p95 1.1s2026-10-23 UTC: p95 1.0s2026-10-24 UTC: p95 974ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.2s2026-10-27 UTC: p95 926ms2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 868ms2026-10-30 UTC: p95 866ms2026-10-31 UTC: p95 602ms2026-11-01 UTC: p95 950ms2026-11-02 UTC: p95 818ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.1s
Oct 7Oct 21Nov 5
Southeast Asia
3.2sp95 · latest
5s2.5s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.6s2026-10-08 UTC: p95 1.3s2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.5s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.3s2026-10-13 UTC: p95 1.4s2026-10-14 UTC: p95 1.5s2026-10-15 UTC: p95 1.6s2026-10-16 UTC: p95 1.3s2026-10-17 UTC: p95 1.9s2026-10-18 UTC: p95 1.5s2026-10-19 UTC: p95 3.5s2026-10-20 UTC: p95 3.5s2026-10-21 UTC: p95 3.3s2026-10-22 UTC: p95 3.6s2026-10-23 UTC: p95 3.1s2026-10-24 UTC: p95 3.4s2026-10-25 UTC: p95 3.3s2026-10-26 UTC: p95 3.8s2026-10-27 UTC: p95 3.2s2026-10-28 UTC: p95 3.0s2026-10-29 UTC: p95 3.3s2026-10-30 UTC: p95 3.4s2026-10-31 UTC: p95 2.7s2026-11-01 UTC: p95 2.8s2026-11-02 UTC: p95 2.6s2026-11-03 UTC: p95 3.2s2026-11-04 UTC: p95 3.0s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
Australia
3.2sp95 · latest
5s2.5s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.3s2026-10-08 UTC: p95 1.2s2026-10-09 UTC: p95 1.4s2026-10-10 UTC: p95 1.3s2026-10-11 UTC: p95 1.3s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.2s2026-10-14 UTC: p95 1.1s2026-10-15 UTC: p95 1.2s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 3.5s2026-10-18 UTC: p95 3.4s2026-10-19 UTC: p95 2.8s2026-10-20 UTC: p95 3.9s2026-10-21 UTC: p95 2.9s2026-10-22 UTC: p95 2.8s2026-10-23 UTC: p95 2.8s2026-10-24 UTC: p95 2.8s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 2.7s2026-10-27 UTC: p95 2.6s2026-10-28 UTC: p95 2.8s2026-10-29 UTC: p95 2.8s2026-10-30 UTC: p95 3.0s2026-10-31 UTC: p95 2.3s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 3.7s2026-11-03 UTC: p95 4.0s2026-11-04 UTC: p95 4.0s2026-11-05 UTC: p95 3.2s
Oct 7Oct 21Nov 5
South America
3.6sp95 · latest
10s5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 10s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.0s2026-10-08 UTC: p95 929ms2026-10-09 UTC: p95 1.2s2026-10-10 UTC: p95 1.0s2026-10-11 UTC: p95 1.0s2026-10-12 UTC: p95 1.0s2026-10-13 UTC: p95 1.3s2026-10-14 UTC: p95 1.4s2026-10-15 UTC: p95 824ms2026-10-16 UTC: p95 650ms2026-10-17 UTC: p95 1.5s2026-10-18 UTC: p95 2.0s2026-10-19 UTC: p95 2.1s2026-10-20 UTC: p95 2.5s2026-10-21 UTC: p95 2.3s2026-10-22 UTC: p95 2.5s2026-10-23 UTC: p95 8.1s2026-10-24 UTC: p95 2.7s2026-10-25 UTC: p95 2.8s2026-10-26 UTC: p95 3.1s2026-10-27 UTC: p95 2.7s2026-10-28 UTC: p95 2.7s2026-10-29 UTC: p95 3.1s2026-10-30 UTC: p95 2.8s2026-10-31 UTC: p95 1.3s2026-11-01 UTC: p95 1.2s2026-11-02 UTC: p95 2.3s2026-11-03 UTC: p95 2.0s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 3.6s
Oct 7Oct 21Nov 5

Check your own site while you wait on Intercom

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Intercom. It cannot diagnose Intercom's own systems.

What we measured, function by function

Intercom answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • EU regionUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • Help centerUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • InboxUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Intercom reports an incident on its status page, and again when it reports it resolved.

Get an email when Intercom reports an incident

Email me when Intercom reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Intercom's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 728msstatus code: 401checked: Nov 5, 2026, 1:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Intercom normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 3136msstatus code: 401checked: Nov 5, 2026, 1:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Intercom normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Checks passinglatency: 416msstatus code: 401checked: Nov 5, 2026, 1:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Intercom normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 884msstatus code: 401checked: Nov 5, 2026, 1:51 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Intercom normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 1174msstatus code: 401checked: Nov 5, 2026, 1:54 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Intercom normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 1392msstatus code: 401checked: Nov 5, 2026, 1:56 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Intercom normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Checks passinglatency: 967msstatus code: 401checked: Nov 5, 2026, 2:00 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Intercom normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2234msstatus code: 401checked: Nov 5, 2026, 1:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Intercom normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Checks passinglatency: 2364msstatus code: 401checked: Nov 5, 2026, 1:58 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Intercom normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 2589msstatus code: 401checked: Nov 5, 2026, 1:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Intercom normally. We do not have enough reports from Australia to say anything about what people there are seeing.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Intercom, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Intercom yet, which is not evidence that nothing is wrong.

Recent probe events

Slow Fin Procedures , 24mdeclared on their status page2026-10-30
Customer contact details showing up as "Redacted" in the Intercom Inbox, 12mdeclared on their status page2026-10-14
Issues with Fin for Salesforce, 5h 27mdeclared on their status page2026-09-16
Messenger Help Articles not displaying, 9mdeclared on their status page2026-09-09
Fin intermittent failures responding to first conversation messages, 39mdeclared on their status page2026-09-04
Fin failures in Australia region, 12mdeclared on their status page2026-09-03
Fin not answering in the USA region, 23mdeclared on their status page2026-08-26
Issues with Shopify integration, 33mdeclared on their status page2026-08-19

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Intercom since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Intercom covering any window you pick, with our check readings and Intercom's own claim at the time, side by side.

Full check history for Intercom: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Intercom uptime by RealUptime's checksLive, from this page's own readings.
[![Intercom uptime by RealUptime's checks](https://realuptime.io/outages/intercom/badge.svg?days=30)](https://realuptime.io/outages/intercom)
<a href="https://realuptime.io/outages/intercom"><img src="https://realuptime.io/outages/intercom/badge.svg?days=30" alt="Intercom uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Intercom down?", https://realuptime.io/outages/intercom. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.intercom.io/me
secondary
https://www.intercom.com/
secondary
https://app.intercom.com/admins/sign_in
secondary
https://www.intercom.com/help/en/
secondary
https://api.eu.intercom.io/me

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.intercom.io

RealUptime is not affiliated with Intercom; the name identifies what we checked, and nothing here speaks for Intercom's own team. We send a single web request to Intercom from 10 regions on our own schedule and time the response. We do not see inside Intercom's systems, do not use an account or real transaction, and are not the same signal Intercom's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Intercom is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.