- Level
- confirmed
- Worst impact
- Partial outage
- Regions
- us
- Down Index
- 46of 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 23m it lasted.
Anything that failed between 2026-08-26 14:26 UTC and 2026-08-26 14:49 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 3
- investigating
We're investigating Fin not answering conversations in the USA hosting region.
provider
- identified
We're seeing partial recovery for Fin answering questions.
provider
- resolved
Between 14:15 - 14:41 UTC Fin was slow to respond to conversations. We have identified the cause and do not expect recurrence. Apologies for the disruption. There are more details available in the attached root cause analysis document.
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-6715d01446
Is Intercom still down?
No, this incident was resolved 2026-08-26 14:49 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
23m, from 2026-08-26 14:26 UTC to 2026-08-26 14:49 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.