outages.live
Live
FinIncident ·

Elevated errors and latencies in the European hosting region.

ResolvedOfficial update
0

Fin had elevated errors and latencies in the European hosting region. The incident is resolved. It lasted 50 minutes.

State

Resolved

Started

Lasted

50 min

Worst impact

Partial outage

Timeline

2 updates
15:3615:4916:0116:1416:26
Partial outageUpdate postedTimes in UTC

Investigating

50 min 100%

Updates

Times in UTC

As posted by Fin

Resolved

Between 15:27 - 15:35 UTC we experienced an outage of Fin and the Intercom helpdesk in the European hosting region. We will publish a writeup of the outage on our status page.

Investigating

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

9

Days with an incident

9

Median duration

24 min

This incident

2.1× the median

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

5 h 27 min
median 24 min
90 days agoToday

Other Fin incidents

All incidents

Fin·Slow Fin Procedures

Fin Procedures is back to normal.

Resolved

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.

Resolved

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)

Resolved

Fin·Messenger Help Articles not displaying

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

Resolved

Fin·Fin intermittent failures responding to first conversation messages

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

Resolved

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