Intercom is down
Fin reports that Intercom is down. The outage affects customers hosted in the US region. Fin later reports a database issue in the US region and stops the query that caused it. Fin states that the incident is resolved. The outage lasted 33 minutes.
State
Resolved
Started
Lasted
33 min
Worst impact
Major outage
Timeline
5 updatesInvestigating
24 min 72%
Monitoring
9 min 28%
Updates
Times in UTCAs posted by Fin
We’re no longer seeing issues related to this incident, and all affected components are operating normally.
We’ve traced the US-region disruption to a single query saturating database replicas. We’ve stopped the workload generating that query and services are fully recovered and operating normally.
We’ve identified a database issue in the US region and remediated. We’re now seeing signs of recovery and are monitoring closely to ensure service continues to return to normal.
We’re seeing this outage primarily affecting customers hosted in the US region; other regions currently appear unaffected. We’re continuing to investigate the underlying cause.
Intercom and Fin are experiencing difficulties. Our team is aware of the issue and are currently investigating. We will update you here when we have more information.
Fin in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
11
Median duration
33 min
This incident
About the median
Other Fin incidents
All incidentsFin·Delays in outbound email delivery
Fin reports delays in outbound email delivery to Microsoft recipients. The incident is resolved. It lasted about 21 hours and 20 minutes.
Fin·Elevated errors and latencies in the European hosting region.
Fin had elevated errors and latencies in the European hosting region. The incident is resolved. It lasted 50 minutes.
Fin·Slow Fin Procedures
Fin Procedures is back to normal.
Fin·Customer contact details showing up as "Redacted" in the Intercom Inbox
Between 16:50 UTC and 17:39 UTC contact details were replaced with "Redacted" in the Intercom Helpdesk for teammates missing explicit permissions to view contact details. We're sorry for the disruption.
Fin·Issues with Fin for Salesforce
All services are presumed to be restored to normal operations. For more information please refer to [this status page.](https://status.salesforce.com/incidents/20004433)
Follow Fin
Your coding agent knows when Fin is down, and tells you when a failure is theirs, not yours. You can also get Fin incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "fin" and tell me if Fin has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=fin/feed subscribe https://outages.live/feed.xml?providers=finFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane