Intercom outage: Fin not answering in the USA region

1. resolvedAug 26, 2026, 14:49 UTC

   Between 14:15 - 14:41 UTC Fin was slow to respond to conversations. We have identified the cause and do not expect recurrence. Apologies for the disruption. There are more details available in the attached root cause analysis document.

2. identifiedAug 26, 2026, 14:39 UTC

   We're seeing partial recovery for Fin answering questions.

3. investigatingAug 26, 2026, 14:26 UTC

   We're investigating Fin not answering conversations in the USA hosting region.

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.

• Smartsheet: Sheets in Smartsheet US are failing to loadCritical · Aug 26, 2026, 13:28 UTC
• OVHcloud: [GLOBAL][Data & Analytics] - Cloud Database Incident NotificationMajor · Aug 25, 2026, 21:25 UTC
• Figma: Figma MCP DisruptionMajor · Aug 26, 2026, 12:08 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 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