Live

Intercom is down

0

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 updates
19:1519:2319:3219:4019:48
Major outageUpdate postedTimes in UTC

Investigating

24 min 72%

Monitoring

9 min 28%

Updates

Times in UTC

As posted by Fin

Resolved

We’re no longer seeing issues related to this incident, and all affected components are operating normally.

Monitoring

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.

Monitoring

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.

Investigating

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.

Investigating

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 history
90 days agoToday

Incidents in 90 days

11

Days with an incident

11

Median duration

33 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 h 20 min
median 33 min
90 days agoToday

Other Fin incidents

All incidents

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=fin
Slack
/feed subscribe https://outages.live/feed.xml?providers=fin

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane