- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 37of 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 31m it lasted.
Anything that failed between 2026-04-15 16:57 UTC and 2026-04-15 17:29 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
Fin is currently experiencing delayed response times. Our team is aware of the issue and are currently investigating. We will update you here when we have more information.
provider
- identified
We have identified the root cause of the issue and are implementing a fix. We’ll update you here once we’ve confirmed our fix has been effective.
provider
- resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [team@intercom.io](mailto:team@intercom.io) if you have any further questions or if you’re still seeing any unexpected behaviour
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-86ba2c0b99
Is Intercom still down?
No, this incident was resolved 2026-04-15 17:29 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
31m, from 2026-04-15 16:57 UTC to 2026-04-15 17:29 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.