Issues with Shopify integration
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.
The latest update from Fin.
State
Resolved
Started
73 d ago
2026-08-19 23:12 UTC
Lasted
33 min
until 2026-08-19 23:45 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
29 min 87%
Monitoring
4 min 13%
Updates
Times in UTCAs posted by Fin
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.
We have implemented a fix and are monitoring. We’ll let you know when we are confident in our recovery.
We're seeing issues with our Shopify integration. Our team is aware and investigating the issue. We’ll update you here as soon as we have more specific information.
Fin in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
8
Median duration
24 min
This incident
1.4× the median
Other Fin incidents
All incidentsFin·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)
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
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
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.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.
https://outages.cc/feed.xml?providers=fin/feed subscribe https://outages.cc/feed.xml?providers=finFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane