Intercom incident: Fin is experiencing issues

1. resolvedApr 15, 2026, 17:29 UTC

   This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to [[email protected]](mailto:[email protected]) if you have any further questions or if you’re still seeing any unexpected behaviour

2. identifiedApr 15, 2026, 17:20 UTC

   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.

3. investigatingApr 15, 2026, 16:57 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Intercom's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• 1Password: SSO sign-in failing on some attempts for some usersMajor · Apr 13, 2026, 17:24 UTC
• GitBook: Git Sync executions are delayed due to third-party outageMajor · Apr 15, 2026, 15:34 UTC
• Inngest: Delays in function run schedulingMinor · Apr 15, 2026, 12:15 UTC
• ReadMe: Slow page performanceMinor · Apr 15, 2026, 17:18 UTC

How often does Intercom have incidents?

Intercom reported 9 incidents in the last 90 days, 3 of them major or critical. A typical incident lasted 24 min. See Intercom's uptime and incident history