Skip to main content
Vendor reliability

Vendor record

Intercom

Vendor reports Operational

Checked

Front door check counts and Intercom’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.

Front door checks

We send a request to a documented Intercom endpoint and count the checks that got the answer it is documented to give.

  • Front door reachable in 1,724 of 1,724 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.

    Endpoint checked
    api.intercom.io
    Scope
    apiNo vendor region
    First check in this window
    Latest clear answer

Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Intercom product, region or your app worked.

How we count front door checks

Shorter disruptions

Our checks are 15 minutes apart, so they miss disruptions shorter than that. Datadog runs a separate outage tracker that may show disruptions our checks cannot see.

Independent outage detection for Intercom: Datadog’s Updog(opens in a new tab)

CheckUpstream is not affiliated with Datadog.

Intercom says

Incident posts from Intercom’s status page, with its titles, impact levels and times. They say what Intercom chose to post, not what reached your app.

A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.

0

incidents Intercom posted, last 90 days

All vendors’ incidents

Most recent records · all dates

No incidents recorded

Intercom has posted nothing we recorded. That is an empty history, not evidence of uninterrupted service.

Your code, your dependencies

See which of your code paths call Intercom

Connect GitHub or GitLab to find where your public or private repository uses Intercom. Review each match and your alert settings.

Connect a repository

Free to start. No credit card.

Use this record on your site

Add Intercom status to your page.

Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.

Appearance
Detail
Preview · IntercomStatus only

For HTML pages that permit CheckUpstream frames. Loads a snapshot; reload the containing page for a newer reading. Theme and detail settings apply to this format.

Iframe snippet
<iframe src="https://checkupstream.com/embed/intercom?layout=card" style="border:0;width:320px;max-width:100%;height:96px" loading="lazy" title="Intercom status badge"></iframe>

Frequently Asked Questions

Is Intercom currently down?

Intercom's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.

When did Intercom last have an outage?

We have no closed incident record for Intercom in the past 12 months. Missing records do not establish that the service had no incidents.

Does CheckUpstream publish an uptime percentage for Intercom?

No. CheckUpstream checks Intercom’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.

How do I monitor Intercom in production?

Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.

How does CheckUpstream track Intercom?

This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.