- Detected by Pingoru
- Jun 16, 2026, 10:15 AM UTC
- Resolved
- Jun 16, 2026, 11:32 AM UTC
- Duration
- 1h 16m
Affected: Payments
Timeline · 2 updates
-
identified Jun 16, 2026, 10:15 AM UTC
The issue has been identified and we are currently working on a solution.
-
resolved Jun 16, 2026, 11:32 AM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2026, 09:45 AM UTC
- Resolved
- Jun 03, 2026, 08:31 AM UTC
- Duration
- 22h 46m
Affected: Payments
Timeline · 3 updates
-
investigating Jun 02, 2026, 09:45 AM UTC
We are currently investigating an issue with Payment Initiation.
-
monitoring Jun 02, 2026, 10:25 AM UTC
Service is currently recovering and we are actively monitoring the situation.
-
resolved Jun 03, 2026, 08:31 AM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 12:35 AM UTC
- Resolved
- Jun 01, 2026, 04:53 AM UTC
- Duration
- 4h 18m
Affected: Other
Timeline · 2 updates
-
identified Jun 01, 2026, 12:35 AM UTC
The issue has been identified and we are currently working on a solution.
-
resolved Jun 01, 2026, 04:53 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 28, 2026, 04:47 PM UTC
- Resolved
- May 28, 2026, 06:02 PM UTC
- Duration
- 1h 15m
Affected: Settlement accounts
Timeline · 2 updates
-
identified May 28, 2026, 04:47 PM UTC
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.
-
resolved May 28, 2026, 06:02 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 21, 2026, 09:52 PM UTC
- Resolved
- May 21, 2026, 10:47 PM UTC
- Duration
- 55m
Affected: Payments
Timeline · 2 updates
-
investigating May 21, 2026, 09:52 PM UTC
We are currently investigating an issue with payments in German market.
-
resolved May 21, 2026, 10:47 PM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- May 19, 2026, 09:53 AM UTC
- Resolved
- May 22, 2026, 07:39 AM UTC
- Duration
- 2d 21h
Affected: Settlement accounts
Timeline · 3 updates
-
investigating May 19, 2026, 09:53 AM UTC
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.
-
monitoring May 21, 2026, 01:29 PM UTC
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.
-
resolved May 22, 2026, 07:39 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 11, 2026, 01:32 PM UTC
- Resolved
- May 11, 2026, 02:19 PM UTC
- Duration
- 46m
Affected: Transactions
Timeline · 2 updates
-
investigating May 11, 2026, 01:32 PM UTC
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.
-
resolved May 11, 2026, 02:19 PM UTC
The issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 09:16 PM UTC
- Resolved
- Mar 20, 2026, 08:12 AM UTC
- Duration
- 10h 55m
Affected: Payments
Timeline · 2 updates
-
investigating Mar 19, 2026, 09:16 PM UTC
We are currently looking into an issue with Nordea bulk payments. The initiation for the SE market has been failing for about 3 hours.
-
resolved Mar 20, 2026, 08:12 AM UTC
The issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Mar 03, 2026, 01:03 PM UTC
- Resolved
- Mar 03, 2026, 01:03 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Mar 03, 2026, 01:03 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 03:53 PM UTC
- Resolved
- Feb 04, 2026, 08:09 AM UTC
- Duration
- 16h 16m
Affected: Other
Timeline · 2 updates
-
investigating Feb 03, 2026, 03:53 PM UTC
We are currently investigating an issue with Analytics in Tink Console.
-
resolved Feb 04, 2026, 08:09 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 03, 2026, 10:42 AM UTC
- Resolved
- Feb 03, 2026, 10:42 AM UTC
- Duration
- —
Affected: Payments
Timeline · 1 update
-
resolved Feb 03, 2026, 10:42 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 09:33 AM UTC
- Resolved
- Jan 21, 2026, 09:47 AM UTC
- Duration
- 13m
Affected: PaymentsSettlement accountsAccount CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense CheckMoney ManagerData EnrichmentBusiness Manager
Timeline · 2 updates
-
investigating Jan 21, 2026, 09:33 AM UTC
We’re currently experiencing degraded performance affecting multiple products since 10:01 CET. Some users may encounter issues with availability.
-
resolved Jan 21, 2026, 09:47 AM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 10:14 AM UTC
- Resolved
- Dec 08, 2025, 10:14 AM UTC
- Duration
- —
Affected: Data Enrichment
Timeline · 1 update
-
resolved Dec 08, 2025, 10:14 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2025, 08:22 PM UTC
- Resolved
- Nov 20, 2025, 08:22 PM UTC
- Duration
- —
Affected: Transactions
Timeline · 1 update
-
resolved Nov 20, 2025, 08:22 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Nov 20, 2025, 11:09 AM UTC
- Resolved
- Nov 20, 2025, 03:37 PM UTC
- Duration
- 4h 28m
Affected: PaymentsSettlement accountsAccount CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense Check
Timeline · 4 updates
Read the full incident report →
Critical November 5, 2025 - Detected by Pingoru
- Nov 05, 2025, 09:56 AM UTC
- Resolved
- Nov 05, 2025, 10:41 AM UTC
- Duration
- 44m
Affected: TransactionsBusiness Transactions
Timeline · 2 updates
-
investigating Nov 05, 2025, 09:56 AM UTC
We are currently looking into a full auto refresh outage for the Oxford production environment. An update will be posted as quickly as possible.
-
resolved Nov 05, 2025, 10:41 AM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Oct 13, 2025, 12:39 PM UTC
- Resolved
- Oct 13, 2025, 04:13 PM UTC
- Duration
- 3h 34m
Affected: PaymentsSettlement accountsAccount CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense CheckMoney ManagerData EnrichmentBusiness Manager
Timeline · 2 updates
-
investigating Oct 13, 2025, 12:39 PM UTC
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.
-
resolved Oct 13, 2025, 04:13 PM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
Notice September 25, 2025 - Detected by Pingoru
- Sep 25, 2025, 11:52 AM UTC
- Resolved
- Sep 25, 2025, 11:52 AM UTC
- Duration
- —
Affected: Money Manager
Timeline · 1 update
-
resolved Sep 25, 2025, 11:52 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 08:49 AM UTC
- Resolved
- Sep 25, 2025, 09:50 AM UTC
- Duration
- 1h
Affected: Payments
Timeline · 3 updates
-
investigating Sep 25, 2025, 08:49 AM UTC
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.
-
monitoring Sep 25, 2025, 09:28 AM UTC
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.
-
resolved Sep 25, 2025, 09:50 AM UTC
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.
Read the full incident report →
Critical September 6, 2025 - Detected by Pingoru
- Sep 06, 2025, 02:18 PM UTC
- Resolved
- Sep 08, 2025, 11:59 AM UTC
- Duration
- 1d 21h
Affected: Other
Timeline · 3 updates
-
investigating Sep 06, 2025, 02:18 PM UTC
We are currently investigating an issue with Tink Console.
-
monitoring Sep 06, 2025, 02:48 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 08, 2025, 11:59 AM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 09:38 AM UTC
- Resolved
- Aug 20, 2025, 09:38 AM UTC
- Duration
- —
Affected: Account CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense Check
Timeline · 1 update
-
resolved Aug 20, 2025, 09:38 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2025, 09:58 AM UTC
- Resolved
- Aug 11, 2025, 10:20 AM UTC
- Duration
- 21m
Affected: PaymentsAccount CheckTransactionsIncome CheckRisk Insights
Timeline · 3 updates
-
investigating Aug 11, 2025, 09:58 AM UTC
We are currently investigating an issue that is affecting several Tink products. See details for the full list of affected products.
-
resolved Aug 11, 2025, 10:20 AM UTC
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.
-
postmortem Aug 12, 2025, 06:13 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2025, 07:19 AM UTC
- Resolved
- Jun 30, 2025, 07:19 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 30, 2025, 07:19 AM UTC
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.
Read the full incident report →
- Detected by Pingoru
- May 27, 2025, 07:47 AM UTC
- Resolved
- May 27, 2025, 07:47 AM UTC
- Duration
- —
Affected: Payments
Timeline · 1 update
-
resolved May 27, 2025, 07:47 AM UTC
Between 09:03 CET and 09:06 CET Tink has encountered a technical issue that impacted Payments products for multiple markets. The underlying root cause that caused the incident was resolved. We apologize for any problems this issue may have caused.
Read the full incident report →
- Detected by Pingoru
- May 21, 2025, 10:54 AM UTC
- Resolved
- May 21, 2025, 02:17 PM UTC
- Duration
- 3h 22m
Affected: Settlement accounts
Timeline · 2 updates
-
identified May 21, 2025, 10:54 AM UTC
We are currently experiencing degraded performance for Settlement Accounts caused by a 3rd party vendor.
-
resolved May 21, 2025, 02:17 PM UTC
This issue has been resolved. We apologize for the inconvenience.
Read the full incident report →