PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Intercom is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Intercom. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Intercom issues today?

As of Oct 12, 2026 21:28 UTC, 0 users had reported issues with Intercom in the previous 24 hours.

How can I report a Intercom outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Intercom down right now?

UnknownOfficial status last polled Sep 7, 2026 18:41 UTCintercom.com Official status page

Intercom customer messaging

Are you on the Intercom team and see something inaccurate? Report it to us. We respond within one business day.

Is Intercom down right now?

Unknown. Intercom does not have a conclusive current status. A single-runtime HTTP reachability check succeeded; no fresh official status confirms whole-service health. No current vendor status signal: vendor status was last polled on 2026-09-07, more than 7 days ago. The most recent attempt on 2026-10-12 could not be acquired.

Status as of Oct 12, 2026 21:28 UTC

Unknown

Intercom: status unknown

As of Oct 12, 2026 21:28 UTC

No product check is currently qualified to corroborate an incident for this service. Overall service status has not been established.

Reports 24h

Last incident

May 4, 2026 11:33 UTC

Trend

0/15m

Monitoring

Coverage gap

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Intercom.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Intercom. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Intercom outage on May 4 — 24-minute disruption

May 4, 11:08 AM → May 4, 11:33 AM · 24 minutes · medium

An incident affecting Intercom services was detected through user reports. The disruption lasted approximately 24 minutes. Services were fully restored by 2026-05-04T11:33:00.303Z.

Duration

24 minutes

tracked by PulseWatch

Impact

Users reported experiencing issues with Intercom services during the incident. While specific details regarding affected features or regions were not consistently recorded, the reports indicated a period of reduced functionality or unavailability for some users. The incident was detected through these user reports, which peaked at 4 reports within a 15-minute window.

Incident timeline

May 4, 11:08 AM
PulseWatch detected elevated report volume (medium severity)
May 4, 11:13 AM
Status updated: possible issue
May 4, 11:15 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 4, 11:33 AM
Report volume returned to baseline — incident resolved

Reliability

Not measured

30-day uptime

n/a

90-day uptime

n/a

Not calculated: Intercom is unknown, so there is no incident history to measure and no uptime figure is shown.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.