Skip to content

Outage tracker / Intercom

Is Intercom down?

I'm having a problem

Operationalchecked 4 minutes ago

We reached Intercom from all 10 regions we check.

As of Oct 5, 2026, 8:11 PM UTC, Intercom answered RealUptime's probes in all 10 regions that returned a reading.

Functional endpoints verified

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

our independent probeslive · checked Oct 5, 2026, 8:11 PM UTC
US-East212 msOperational
US-West445 msOperational
Europe895 msOperational
Asia-Pacific757 msOperational
US-Central349 msOperational
Canada361 msOperational
UK470 msOperational
Southeast Asia1080 msOperational
Australia1093 msOperational
South America661 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
674msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 554ms2026-09-07 UTC: p95 568ms2026-09-08 UTC: p95 548ms2026-09-09 UTC: p95 534ms2026-09-10 UTC: p95 560ms2026-09-11 UTC: p95 525ms2026-09-12 UTC: p95 601ms2026-09-13 UTC: p95 515ms2026-09-14 UTC: p95 419ms2026-09-15 UTC: p95 333ms2026-09-16 UTC: p95 404ms2026-09-17 UTC: p95 354ms2026-09-18 UTC: p95 347ms2026-09-19 UTC: p95 340ms2026-09-20 UTC: p95 521ms2026-09-21 UTC: p95 417ms2026-09-22 UTC: p95 380ms2026-09-23 UTC: p95 572ms2026-09-24 UTC: p95 656ms2026-09-25 UTC: p95 617ms2026-09-26 UTC: p95 565ms2026-09-27 UTC: p95 348ms2026-09-28 UTC: p95 352ms2026-09-29 UTC: p95 353ms2026-09-30 UTC: p95 340ms2026-10-01 UTC: p95 564ms2026-10-02 UTC: p95 340ms2026-10-03 UTC: p95 611ms2026-10-04 UTC: p95 547ms2026-10-05 UTC: p95 674ms
Sep 6Sep 20Oct 5
US-West
819msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 898ms2026-09-07 UTC: p95 973ms2026-09-08 UTC: p95 811ms2026-09-09 UTC: p95 618ms2026-09-10 UTC: p95 551ms2026-09-11 UTC: p95 602ms2026-09-12 UTC: p95 588ms2026-09-13 UTC: p95 515ms2026-09-14 UTC: p95 434ms2026-09-15 UTC: p95 748ms2026-09-16 UTC: p95 757ms2026-09-17 UTC: p95 816ms2026-09-18 UTC: p95 757ms2026-09-19 UTC: p95 803ms2026-09-20 UTC: p95 804ms2026-09-21 UTC: p95 797ms2026-09-22 UTC: p95 838ms2026-09-23 UTC: p95 674ms2026-09-24 UTC: p95 622ms2026-09-25 UTC: p95 653ms2026-09-26 UTC: p95 660ms2026-09-27 UTC: p95 542ms2026-09-28 UTC: p95 574ms2026-09-29 UTC: p95 568ms2026-09-30 UTC: p95 835ms2026-10-01 UTC: p95 733ms2026-10-02 UTC: p95 631ms2026-10-03 UTC: p95 780ms2026-10-04 UTC: p95 801ms2026-10-05 UTC: p95 819ms
Sep 6Sep 20Oct 5
Europe
530msp95 · 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-09-06 UTC: p95 559ms2026-09-07 UTC: p95 575ms2026-09-08 UTC: p95 627ms2026-09-09 UTC: p95 790ms2026-09-10 UTC: p95 905ms2026-09-11 UTC: p95 862ms2026-09-12 UTC: p95 724ms2026-09-13 UTC: p95 866ms2026-09-14 UTC: p95 881ms2026-09-15 UTC: p95 838ms2026-09-16 UTC: p95 599ms2026-09-17 UTC: p95 662ms2026-09-18 UTC: p95 544ms2026-09-19 UTC: p95 511ms2026-09-20 UTC: p95 531ms2026-09-21 UTC: p95 569ms2026-09-22 UTC: p95 692ms2026-09-23 UTC: p95 649ms2026-09-24 UTC: p95 593ms2026-09-25 UTC: p95 635ms2026-09-26 UTC: p95 587ms2026-09-27 UTC: p95 558ms2026-09-28 UTC: p95 594ms2026-09-29 UTC: p95 604ms2026-09-30 UTC: p95 567ms2026-10-01 UTC: p95 547ms2026-10-02 UTC: p95 575ms2026-10-03 UTC: p95 552ms2026-10-04 UTC: p95 842ms2026-10-05 UTC: p95 530ms
Sep 6Sep 20Oct 5
Asia-Pacific
1.1sp95 · 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-09-06 UTC: p95 1.0s2026-09-07 UTC: p95 1.1s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.0s2026-09-10 UTC: p95 1.2s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.2s2026-09-13 UTC: p95 1.2s2026-09-14 UTC: p95 1.2s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.3s2026-09-18 UTC: p95 1.4s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 1.3s2026-09-21 UTC: p95 1.4s2026-09-22 UTC: p95 1.3s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.1s2026-09-25 UTC: p95 1.0s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.3s2026-09-28 UTC: p95 1.3s2026-09-29 UTC: p95 1.3s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.1s2026-10-03 UTC: p95 1.1s2026-10-04 UTC: p95 1.2s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 5
US-Central
510msp95 · 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-06 UTC: p95 585ms2026-09-07 UTC: p95 659ms2026-09-08 UTC: p95 623ms2026-09-09 UTC: p95 622ms2026-09-10 UTC: p95 415ms2026-09-11 UTC: p95 432ms2026-09-12 UTC: p95 578ms2026-09-13 UTC: p95 717ms2026-09-14 UTC: p95 556ms2026-09-15 UTC: p95 549ms2026-09-16 UTC: p95 603ms2026-09-17 UTC: p95 600ms2026-09-18 UTC: p95 643ms2026-09-19 UTC: p95 722ms2026-09-20 UTC: p95 719ms2026-09-21 UTC: p95 676ms2026-09-22 UTC: p95 581ms2026-09-23 UTC: p95 603ms2026-09-24 UTC: p95 648ms2026-09-25 UTC: p95 544ms2026-09-26 UTC: p95 587ms2026-09-27 UTC: p95 638ms2026-09-28 UTC: p95 645ms2026-09-29 UTC: p95 479ms2026-09-30 UTC: p95 708ms2026-10-01 UTC: p95 500ms2026-10-02 UTC: p95 478ms2026-10-03 UTC: p95 528ms2026-10-04 UTC: p95 468ms2026-10-05 UTC: p95 510ms
Sep 6Sep 20Oct 5
Canada
655msp95 · 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-06 UTC: p95 477ms2026-09-07 UTC: p95 512ms2026-09-08 UTC: p95 416ms2026-09-09 UTC: p95 437ms2026-09-10 UTC: p95 447ms2026-09-11 UTC: p95 505ms2026-09-12 UTC: p95 418ms2026-09-13 UTC: p95 475ms2026-09-14 UTC: p95 444ms2026-09-15 UTC: p95 414ms2026-09-16 UTC: p95 389ms2026-09-17 UTC: p95 424ms2026-09-18 UTC: p95 480ms2026-09-19 UTC: p95 455ms2026-09-20 UTC: p95 466ms2026-09-21 UTC: p95 488ms2026-09-22 UTC: p95 373ms2026-09-23 UTC: p95 532ms2026-09-24 UTC: p95 730ms2026-09-25 UTC: p95 525ms2026-09-26 UTC: p95 507ms2026-09-27 UTC: p95 501ms2026-09-28 UTC: p95 436ms2026-09-29 UTC: p95 419ms2026-09-30 UTC: p95 446ms2026-10-01 UTC: p95 529ms2026-10-02 UTC: p95 497ms2026-10-03 UTC: p95 471ms2026-10-04 UTC: p95 559ms2026-10-05 UTC: p95 655ms
Sep 6Sep 20Oct 5
UK
472msp95 · 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-06 UTC: p95 433ms2026-09-07 UTC: p95 441ms2026-09-08 UTC: p95 431ms2026-09-09 UTC: p95 471ms2026-09-10 UTC: p95 426ms2026-09-11 UTC: p95 412ms2026-09-12 UTC: p95 419ms2026-09-13 UTC: p95 396ms2026-09-14 UTC: p95 345ms2026-09-15 UTC: p95 359ms2026-09-16 UTC: p95 377ms2026-09-17 UTC: p95 385ms2026-09-18 UTC: p95 383ms2026-09-19 UTC: p95 367ms2026-09-20 UTC: p95 371ms2026-09-21 UTC: p95 353ms2026-09-22 UTC: p95 364ms2026-09-23 UTC: p95 362ms2026-09-24 UTC: p95 373ms2026-09-25 UTC: p95 359ms2026-09-26 UTC: p95 474ms2026-09-27 UTC: p95 491ms2026-09-28 UTC: p95 378ms2026-09-29 UTC: p95 408ms2026-09-30 UTC: p95 435ms2026-10-01 UTC: p95 444ms2026-10-02 UTC: p95 458ms2026-10-03 UTC: p95 540ms2026-10-04 UTC: p95 513ms2026-10-05 UTC: p95 472ms
Sep 6Sep 20Oct 5
Southeast Asia
1.4sp95 · 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-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.3s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.3s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.5s2026-09-12 UTC: p95 1.4s2026-09-13 UTC: p95 1.3s2026-09-14 UTC: p95 1.6s2026-09-15 UTC: p95 1.4s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.6s2026-09-18 UTC: p95 2.0s2026-09-19 UTC: p95 1.7s2026-09-20 UTC: p95 1.7s2026-09-21 UTC: p95 3.3s2026-09-22 UTC: p95 2.8s2026-09-23 UTC: p95 2.9s2026-09-24 UTC: p95 3.1s2026-09-25 UTC: p95 2.7s2026-09-26 UTC: p95 2.8s2026-09-27 UTC: p95 2.5s2026-09-28 UTC: p95 2.7s2026-09-29 UTC: p95 1.6s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.4s2026-10-02 UTC: p95 1.5s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.5s2026-10-05 UTC: p95 1.4s
Sep 6Sep 20Oct 5
Australia
1.3sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.6s2026-09-07 UTC: p95 1.4s2026-09-08 UTC: p95 1.4s2026-09-09 UTC: p95 1.4s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.8s2026-09-12 UTC: p95 1.8s2026-09-13 UTC: p95 1.8s2026-09-14 UTC: p95 1.3s2026-09-15 UTC: p95 1.2s2026-09-16 UTC: p95 1.3s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.2s2026-09-19 UTC: p95 1.4s2026-09-20 UTC: p95 1.1s2026-09-21 UTC: p95 1.5s2026-09-22 UTC: p95 1.4s2026-09-23 UTC: p95 1.4s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.4s2026-09-26 UTC: p95 1.6s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.3s2026-10-01 UTC: p95 1.7s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 1.4s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.3s
Sep 6Sep 20Oct 5
South America
1.1sp95 · latest
2.5s1.3s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 1.3s2026-09-07 UTC: p95 1.5s2026-09-08 UTC: p95 1.5s2026-09-09 UTC: p95 1.5s2026-09-10 UTC: p95 1.4s2026-09-11 UTC: p95 1.3s2026-09-12 UTC: p95 1.3s2026-09-13 UTC: p95 1.5s2026-09-14 UTC: p95 1.4s2026-09-15 UTC: p95 1.3s2026-09-16 UTC: p95 1.1s2026-09-17 UTC: p95 1.2s2026-09-18 UTC: p95 1.1s2026-09-19 UTC: p95 1.3s2026-09-20 UTC: p95 993ms2026-09-21 UTC: p95 983ms2026-09-22 UTC: p95 1.0s2026-09-23 UTC: p95 1.1s2026-09-24 UTC: p95 1.2s2026-09-25 UTC: p95 1.5s2026-09-26 UTC: p95 1.3s2026-09-27 UTC: p95 1.2s2026-09-28 UTC: p95 1.2s2026-09-29 UTC: p95 1.2s2026-09-30 UTC: p95 1.6s2026-10-01 UTC: p95 1.1s2026-10-02 UTC: p95 1.4s2026-10-03 UTC: p95 2.1s2026-10-04 UTC: p95 1.3s2026-10-05 UTC: p95 1.1s
Sep 6Sep 20Oct 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

Get an email when we see Intercom go down, and when it is back

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.

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: 212msstatus code: 401checked: Oct 5, 2026, 8:09 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
      Operationallatency: 445msstatus code: 401checked: Oct 5, 2026, 8:08 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
      Operationallatency: 349msstatus code: 401checked: Oct 5, 2026, 8:06 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
      Operationallatency: 361msstatus code: 401checked: Oct 5, 2026, 8:00 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
    Operationallatency: 661msstatus code: 401checked: Oct 5, 2026, 8:03 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
    OperationalEurope, UK
    • Europe
      Operationallatency: 895msstatus code: 401checked: Oct 5, 2026, 8:10 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
      Operationallatency: 470msstatus code: 401checked: Oct 5, 2026, 8:08 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
    OperationalAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 757msstatus code: 401checked: Oct 5, 2026, 8:11 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
      Operationallatency: 1080msstatus code: 401checked: Oct 5, 2026, 7:57 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
      Operationallatency: 1093msstatus code: 401checked: Oct 5, 2026, 7:59 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 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

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 last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 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.