- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 43of 100
What to do
Check whether you use Intercom in us. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 8h 17m it lasted.
Anything that failed between 2026-05-21 11:09 UTC and 2026-05-21 19:25 UTC may need a replay.Subscribe to Intercom's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=intercom works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Intercom 2
- identified
Workspaces in the USA hosting region may be experiencing incomplete historical data in reporting features since May 19th. We are backfilling data and should be up to date later today.
provider
- resolved
The issue is resolved, reporting data is up to date.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-afce7b99e9
Is Intercom still down?
No, this incident was resolved 2026-05-21 19:25 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
8h 17m, from 2026-05-21 11:09 UTC to 2026-05-21 19:25 UTC, by the times Intercom posted.
What was affected?
Intercom named in us.
What caused it?
Intercom hasn't published a root cause. If it does, it shows here.
Where does this come from?
Intercom's official status page, https://www.finstatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.