Live

Fin Voice Degraded Performance

0

Fin Voice gives degraded performance, and customers may have issues on Fin Voice calls. Other components are not impacted. Fin reports the status as monitoring and says a third party LLM provider has an incident.

State

Monitoring

Started

Ongoing for

21 min

Worst impact

Degraded

Timeline

1 update
16:2716:3216:3716:4216:47
DegradedUpdate postedTimes in UTC

Monitoring

21 min 100%

Updates

Times in UTC

As posted by Fin

Monitoring

A third party LLM provider is having an incident impacting Fin Voice's ability to respond correctly. Customers may experience issues when on Fin Voice calls. Other components are not impacted. We'll keep you updated as we learn more.

Fin in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

11

Days with an incident

12

Median duration

28 min

This incident

27% shorter than the median

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

21 h 20 min
median 28 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