- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 40of 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 2h 19m it lasted.
Anything that failed between 2026-06-01 11:03 UTC and 2026-06-01 13:23 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 5
- investigating
We are currently investigating an issue affecting a small subset of customers. Impacted customers may experience inbox loading issues, delays in conversation updates, assignment failures, issues applying attributes, problems sending or receiving messages, or Fin reply disruptions. Our team is actively working to identify the root cause and mitigate the impact. We will provide updates here as soon as more information becomes available.
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
- monitoring
We have implemented a fix and are seeing signs of recovery for some affected customers. We are continuing to monitor the situation closely and will provide another update once we are confident that the full recovery is complete.
provider
- monitoring
We are seeing signs of recovery for more affected customers and are continuing to monitor the situation closely. We will provide another update once we are confident that full recovery is complete.
provider
- resolved
On June 1, 2026, between approximately 11:08 UTC and 13:24 UTC, a small subset of customers experienced degraded performance across Fin and Inbox. During this period, affected customers may have experienced inbox loading issues, delays in conversation updates, message delivery failures, conversation assignment issues, and disruptions to Fin replies. This issue is now 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-39952105b5
Is Intercom still down?
No, this incident was resolved 2026-06-01 13:23 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
2h 19m, from 2026-06-01 11:03 UTC to 2026-06-01 13:23 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.