- Level
- confirmed
- Worst impact
- Major outage
- Regions
- au
- Down Index
- 57of 100
What to do
Check whether you use Intercom in au. 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 12m it lasted.
Anything that failed between 2026-09-03 14:29 UTC and 2026-09-03 14:41 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
We're seeing issues with Fin in Australia. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.
provider
- monitoring
We have implemented a fix and are monitoring for recovery. We’ll let you know when we are confident in our recovery.
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@fin.](mailto:team@fin.ai)ai 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-b5d74b54ad
Is Intercom still down?
No, this incident was resolved 2026-09-03 14:41 UTC. For Intercom's live state, see https://down.guide/intercom.
How long did it last?
12m, from 2026-09-03 14:29 UTC to 2026-09-03 14:41 UTC, by the times Intercom posted.
What was affected?
Intercom named in au.
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.