- Level
- confirmed
- Worst impact
- Major outage
- Regions
- eu
- Down Index
- 51of 100
What to do
Check whether you use Intercom in eu. 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 0m it lasted.
Anything that failed between 2026-04-21 11:13 UTC and 2026-04-21 10:24 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
- investigating
Fin's ability to deliver responses to customers is degraded. We are investigating the issue.
provider
- resolved
On April 21, 2026, between 09:57 UTC and 10:24 UTC, Fin was unable to reliably respond to customer conversations in the EU region. The issue has now been resolved and Fin is operating as expected. We will follow up with a full Root Cause Analysis once we understand the technical details of the issue.
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-46c3998085
Is Intercom still down?
No, this incident was resolved 2026-04-21 10:24 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
0m, from 2026-04-21 11:13 UTC to 2026-04-21 10:24 UTC, by the times Intercom posted.
What was affected?
Intercom named in eu.
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.