- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 42of 100
What to do
Check whether your product depends on Intercom. 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 5h 27m it lasted.
Anything that failed between 2026-09-16 11:51 UTC and 2026-09-16 17:19 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
- monitoring
Fin for Salesforce customers may experience issues due to an upstream error. We have confirmation a fix is being worked on and will update here as soon as we know more.
provider
- resolved
All services are presumed to be restored to normal operations. For more information please refer to [this status page.](https://status.salesforce.com/incidents/20004433)
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-7f2601615f
Is Intercom still down?
No, this incident was resolved 2026-09-16 17:19 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
5h 27m, from 2026-09-16 11:51 UTC to 2026-09-16 17:19 UTC, by the times Intercom posted.
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.