Fin reported "Customer contact details showing up as "Redacted" in the Intercom Inbox" on its status page at 2026-10-14 17:43 UTC.

Fin did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-14 17:43 UTC and ended at 2026-10-14 17:55 UTC. It lasted 12 min.

How do I get alerts for Fin?

Subscribe to the Fin live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Fin. outages.live reads it every few minutes and keeps every update.

FinIncident · 2026-10-14 17:43 UTC

Customer contact details showing up as "Redacted" in the Intercom Inbox

ResolvedOfficial update

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.

The latest update from Fin.

State

Resolved

Started

18 d ago

2026-10-14 17:43 UTC

Lasted

12 min

until 2026-10-14 17:55 UTC

Worst impact

Degraded

Timeline

2 updates

17:4317:4617:4917:5217:55

DegradedUpdate postedTimes in UTC

Investigating

12 min 100%

Updates

Times in UTC

As posted by Fin

Resolved2026-10-14 17:55 UTC

Investigating2026-10-14 17:43 UTC

We're investigating reports of customer contact details showing up as "Redacted" in the Intercom helpdesk.

Fin in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

24 min

This incident

48% shorter than 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.

Resolvedresolved 2 d ago

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)

Resolvedresolved 46 d ago

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

Resolvedresolved 53 d ago

Fin·Fin intermittent failures responding to first conversation messages

Resolvedresolved 58 d ago

Fin·Fin failures in Australia region

Resolvedresolved 59 d ago

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.cc/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.cc/feed.xml?providers=fin

Slack

/feed subscribe https://outages.cc/feed.xml?providers=fin

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane