- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 41of 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 57m it lasted.
Anything that failed between 2026-06-10 13:19 UTC and 2026-06-10 16:15 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
Earlier today at 10:10 UTC many teammates were forced to logout and log back into Intercom. In a small number of cases, server side rate limiting impaired logging back in, causing login loops. We've resolved this issue as of 13:00 UTC. Apologies for any disruption.
provider
- resolved
Open browser tabs with old logins to the Intercom app may be causing ongoing login/logout churn - closing old tabs or restarting web browser will prevent this from happening.
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-c290725f0a
Is Intercom still down?
No, this incident was resolved 2026-06-10 16:15 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
2h 57m, from 2026-06-10 13:19 UTC to 2026-06-10 16:15 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.