Tink had 22 outages in the last 2 years totaling 157h 18m of downtime — averaging 0.9 incidents per month.
There were 22 Tink outages since June 12, 2025 totaling 157h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.
We have identified and are currently investigating an issue with our provider which is affecting both outbound and inbound Faster Payments Service (FPS), which may result in delays.
This incident has been resolved.
We are currently investigating an issue with payments in German market.
This issue has been resolved. We apologize for the inconvenience.
We have identified and are currently investigating an issue with our provider which is affecting both outbound and inbound SEPA payments, which may result in delays.
We continue to monitor an issue affecting both outbound and inbound SEPA payments. While some payments are processing, we cannot yet confirm full service restoration. We are actively investigating and will provide a further update as soon as possible. We apologise for the inconvenience.
We can confirm that the previously identified issue affecting inbound and outbound SEPA payments has now been resolved. Payments are processing as expected. We apologise for the inconvenience caused and thank you for your patience.
We are currently investigating an issue with the account exclusion functionality, as accounts are not being excluded as intended. Further updates will be provided as soon as possible.
The issue has been resolved. We apologize for the inconvenience.
We are currently investigating an issue with Bulk Payments in Sweden.
This issue has been resolved. We apologize for the inconvenience.
We are currently looking into an issue with Nordea bulk payments. The initiation for the SE market has been failing for about 3 hours.
The issue has been resolved. We apologize for the inconvenience.
We experienced a technical issue between 2 March 11:30 CET and 3 March 13:42 CET that caused degraded performance of Transactions and Risk reporting. During this time, some users may have experienced empty reports or missing data when viewing or downloading Transactions and Risk reports. Performance has since returned to normal. We apologize for the inconvenience.
We are currently investigating an issue with Analytics in Tink Console.
This incident has been resolved.
We experienced a technical issue between 10:43 CET and 11:18 CET that caused a degraded performance of the Payment product. During this time some users in the FI and DE markets may have experienced issues with initiating payments. Performance has since returned to normal. We apologize for the inconvenience.
We’re currently experiencing degraded performance affecting multiple products since 10:01 CET. Some users may encounter issues with availability.
This issue has been resolved. We apologize for the inconvenience.
We experienced Temporary outage on data enrichment service between 10.20 and 10:40 CET This resulted in increased of Http 503 responses. Performance has since returned to normal. We apologise for the inconvenience.
We experienced degraded performance between 18:00 CET and 21:00 CET. Degraded performance fetching Transactions. Affected flows: On-demand refreshes and background refreshes Performance has since returned to normal from. We apologize for the inconvenience.
We are currently looking into a full auto refresh outage for the Oxford production environment. An update will be posted as quickly as possible.
This issue has been resolved. We apologize for the inconvenience.
We are currently investigating an issue with Tink Link that is affecting all products in Sweden. Users may experience degraded performance in the desktop journey, specifically with BankID connections across Swedish banks. We are working to identify the root cause and will provide updates as soon as we have more information.
This issue has been resolved. We apologize for the inconvenience.
We experienced delays while generating Insights for Money Manager between 9:20 CET and 13:20 CET today. After a recent library update we identified it caused failures while generating Insights. The changes were rolled back and the service has since returned to normal. Insights will be regenerated. We apologise for the inconvenience.
Since 8:40 CET Tink is experiencing a technical issue that is impacting bulk payments, preventing them from being initiated with the bank. Single payments are working properly and are not affected. We are actively working on resolving this issue.
We found the underlying issue and managed to fix it. We can now see bulk payments being initialized and processed correctly. We will monitor the situation for a while.
We can see bulk payments service is working as expected and no more issues are observed. This incident is now concluded. We are sorry for any problems it has caused.
We are currently investigating an issue with Tink Console.
A fix has been implemented and we are monitoring the results.
This issue has been resolved. We apologize for the inconvenience.
We experienced a technical issue between 11:21 CEST and 11:29 CEST. During the timeframe end users could have experienced a degraded performance of account information products. Performance has since returned to normal. We apologize for the inconvenience.
We are currently investigating an issue that is affecting several Tink products. See details for the full list of affected products.
After some troubleshooting we were able to pinpoint the root cause of the issue and apply a fix. Incident is now resolved. We apologise for any issue this incident has caused.
Introduction On August 11th, between 11:30 CEST and 12:15 CEST, Tink experienced a technical issue that impacted Payments and Account Information products across multiple markets. During the incident, some end-users encountered issues with the availability of certain Tink products. Root Cause Analysis After a thorough investigation, it was identified that there was an error in one of the third-party libraries used to read feature flags, which led to an unrecoverable runtime error in a critical service. This, in turn, caused degradation in the availability of our products. Remediation Once the issue was identified, all affected instances were restarted. To mitigate the issue, a full restart was required, which contributed to the extended downtime for some products. Follow-up actions To prevent similar issues in the future Tink will be implementing the following actions: 1. Downgrade all critical services to a stable version until the third-party library has been fixed.
We experienced an issue with Oxford production between 2025-06-29 5:21:30 AM and 2025-06-29 5:24:30 AM. The cluster was affected by a partial outage that probably affected all products. The Status has since returned to normal. We apologize for the inconvenience.