Skip to content

Outage tracker / Intercom

Is Intercom down?

I'm having a problem

Operationalchecked 1 minute ago

We reached Intercom from all 10 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Intercom (since Aug 22, 2026).

our independent probeslive · checked Sep 5, 2026, 2:06 AM UTC
US-East90 msOperational
US-West557 msOperational
Europe498 msOperational
Asia-Pacific847 msOperational
US-Central303 msOperational
Canada285 msOperational
UK662 msOperational
Southeast Asia1282 msOperational
Australia1409 msOperational
South America413 msOperational
their status pagetheir claim, not our reading

Intercom publishes no status feed we can read, so the only independent reading here is ours on the left.

Intercom response time, by region

US-East
317msp95 · 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-08-22 UTC: p95 720ms2026-08-23 UTC: p95 429ms2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 524ms2026-08-26 UTC: p95 372ms2026-08-27 UTC: p95 413ms2026-08-28 UTC: p95 449ms2026-08-29 UTC: p95 514ms2026-08-30 UTC: p95 419ms2026-08-31 UTC: p95 371ms2026-09-01 UTC: p95 499ms2026-09-02 UTC: p95 369ms2026-09-03 UTC: p95 419ms2026-09-04 UTC: p95 447ms2026-09-05 UTC: p95 317ms
Aug 7Aug 21Sep 5
US-West
651msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 844ms2026-08-23 UTC: p95 721ms2026-08-24 UTC: p95 680ms2026-08-25 UTC: p95 843ms2026-08-26 UTC: p95 639ms2026-08-27 UTC: p95 734ms2026-08-28 UTC: p95 1.1s2026-08-29 UTC: p95 634ms2026-08-30 UTC: p95 945ms2026-08-31 UTC: p95 698ms2026-09-01 UTC: p95 796ms2026-09-02 UTC: p95 695ms2026-09-03 UTC: p95 913ms2026-09-04 UTC: p95 714ms2026-09-05 UTC: p95 651ms
Aug 7Aug 21Sep 5
Europe
630msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 702ms2026-08-23 UTC: p95 845ms2026-08-24 UTC: p95 703ms2026-08-25 UTC: p95 914ms2026-08-26 UTC: p95 694ms2026-08-27 UTC: p95 723ms2026-08-28 UTC: p95 748ms2026-08-29 UTC: p95 798ms2026-08-30 UTC: p95 808ms2026-08-31 UTC: p95 666ms2026-09-01 UTC: p95 812ms2026-09-02 UTC: p95 838ms2026-09-03 UTC: p95 723ms2026-09-04 UTC: p95 859ms2026-09-05 UTC: p95 630ms
Aug 7Aug 21Sep 5
Asia-Pacific
1.3sp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-22 UTC: p95 1.1s2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 1.2s2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 1.3s2026-08-29 UTC: p95 1.3s2026-08-30 UTC: p95 1.3s2026-08-31 UTC: p95 1.2s2026-09-01 UTC: p95 1.2s2026-09-02 UTC: p95 1.5s2026-09-03 UTC: p95 2.0s2026-09-04 UTC: p95 1.3s2026-09-05 UTC: p95 1.3s
Aug 7Aug 21Sep 5
US-Central
541msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 553ms2026-09-04 UTC: p95 617ms2026-09-05 UTC: p95 541ms
Aug 7Aug 21Sep 5
Canada
527msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 621ms2026-09-04 UTC: p95 501ms2026-09-05 UTC: p95 527ms
Aug 7Aug 21Sep 5
UK
644msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 590ms2026-09-04 UTC: p95 609ms2026-09-05 UTC: p95 644ms
Aug 7Aug 21Sep 5
Southeast Asia
1.5sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.8s2026-09-04 UTC: p95 1.5s2026-09-05 UTC: p95 1.5s
Aug 7Aug 21Sep 5
Australia
1.7sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.6s2026-09-04 UTC: p95 2.0s2026-09-05 UTC: p95 1.7s
Aug 7Aug 21Sep 5
South America
832msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.3s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 832ms
Aug 7Aug 21Sep 5

Is it Intercom, or is it you?

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: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
  • APIprimaryUS-East: OperationalUS-West: OperationalEurope: OperationalAsia-Pacific: OperationalUS-Central: OperationalCanada: OperationalUK: OperationalSoutheast Asia: OperationalAustralia: OperationalSouth America: Operational
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 we measured, and what people reported

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 90msstatus code: 401checked: Sep 5, 2026, 2:06 AM 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
      Operationallatency: 557msstatus code: 401checked: Sep 5, 2026, 2:03 AM 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
      Operationallatency: 303msstatus code: 401checked: Sep 5, 2026, 2:04 AM 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
      Operationallatency: 285msstatus code: 401checked: Sep 5, 2026, 2:05 AM 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
    Operationallatency: 413msstatus code: 401checked: Sep 5, 2026, 2:06 AM 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 498msstatus code: 401checked: Sep 5, 2026, 1:58 AM 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
      Operationallatency: 662msstatus code: 401checked: Sep 5, 2026, 1:59 AM 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 847msstatus code: 401checked: Sep 5, 2026, 2:02 AM 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
      Operationallatency: 1282msstatus code: 401checked: Sep 5, 2026, 2:02 AM 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
      Operationallatency: 1409msstatus code: 401checked: Sep 5, 2026, 1:51 AM 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 outages

No outages on record yet for Intercom.

measured 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 measurements and Intercom's own claim at the time, side by side.

Full availability history for Intercom: 90-day availability by region, month-by-month uptime, and every incident 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

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Intercom, and again when they can reach it again. That is our own measurement from ten regions, not Intercom's status page. No account, no card.

Delivery channel

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

Put this badge in your README

Intercom uptime measured by RealUptimeLive, from this page's own readings.
[![Intercom uptime measured by RealUptime](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 measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Intercom's SLA implies, from our measurement

At or above your target

We measured none of downtime for Intercom over the 338h 7m since we started watching it on 2026-08-22, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Intercom's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional: live API
https://api.intercom.io/me
secondary
https://www.intercom.com/
RealUptime is not affiliated with Intercom; the name identifies what we measured, 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 clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.