Störungsverlauf von Tink

Between June 20th, 02:00 CEST and June 22nd, 13:40 CET Tink has experienced degraded performance with webhooks. We have pinpointed the root cause of the issue and resolved it. We are sorry any issues this may have caused.

The issue has been identified and we are currently working on a solution.

This issue has been resolved. We apologize for the inconvenience.

We are currently investigating an issue with Payment Initiation.

Service is currently recovering and we are actively monitoring the situation.

This issue has been resolved. We apologize for the inconvenience.

The issue has been identified and we are currently working on a solution.

This incident has been resolved.

We have identified and are currently investigating an issue with our provider which is affecting 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 are currently investigating an issue with Payment initiations across multiple markets.

This issue has been resolved. We apologize for the inconvenience.

**Introduction**  On 5 March, between 10:31 CET and 10:59 CET, Tink experienced a technical issue that impacted the Payment Initiation service across multiple markets. The issue was detected immediately, and mitigation actions were taken promptly to limit the impact. During the incident window, some end users experienced difficulties when initiating payments.  **Root Cause Analysis**  Following a thorough investigation, it was determined that a recently introduced change contained a defect that caused unexpected request failures within the Payment Initiation service. This resulted in a temporary disruption to payment initiation flows in the affected markets.  **Remediation**  As soon as the issue was identified, the affected deployment was immediately rolled back. This action mitigated the impact and restored normal service functionality.  **Follow-up actions**  To reduce the risk of similar incidents in the future, Tink is taking the following actions:  1. **Extend test coverage for payment initiation scenarios** Further strengthen the pre-deployment validation for payment flows by expanding our end-to-end test coverage for payment flows.

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 a major outage impacting Payments since 17:48 CET. Our team is investigating the issue, and we’ll share updates here as soon as possible.

This issue has been resolved as of 19:01 CET. We apologize for the inconvenience.

# Introduction  On 2 February 2026, between 17:48 and 19:01 CET, Tink experienced a technical issue that affected the availability of all Payments products across all markets. During this period of the incident, end‑users were unable to successfully initiate one‑time or bulk payments.  # Root Cause Analysis  Following a detailed investigation, it was determined that the incident was caused by an availability issue affecting a critical database table. As this table is a required dependency for multiple service flows, all flows relying on it were unable to function during the incident.   # Remediation  Once the issue was identified, a new copy of the database table was created to minimize the total duration of unavailability of our PIS \(Payment Initiation Service\) and restore normal service.  # Follow-up actions  To prevent similar issues in the future, Tink will be implementing the following actions:  1. Review alerting and improve monitoring of database table parameters

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 a technical issue between 15:06 CET and 15:24 CET. During this time users had issues with availability of Tink products. Status has since returned to normal. We apologise for the inconvenience.

# Introduction On 24th November between 15:06 and 15:30 CET Tink experienced a technical issue which impacted all products in all European markets. During the time of the incident, end-users were experiencing issues with initiating payments, fetching transactions, performing account and balance checks, generating risk reports. # Root Cause Analysis After a thorough investigation, it was found that the issue was caused by an attempt to resume a failed backup job on our main production database. Initiating a command to verify data integrity caused a lock on the database. # Remediation Once the issue was identified, the process which was causing the lock was terminated. # Follow-up actions To prevent similar issues in the future, Tink will be implementing the following actions: 1. We are strengthening our internal processes so that any resource-intensive commands meant to be run on production databases should go through internal review with full risk assessment and run on replicas and/or non-production environments first

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 investigating an issue with multiple products affecting all markets.

Service is currently recovering and we are actively monitoring the situation.

This issue has been resolved. We apologize for the inconvenience.

# Introduction  On 20th November between 11:50 and 12:30 CET Tink experienced a technical issue which impacted AIS and PIS products in all markets. During the time of the incident, end-users were experiencing issues with initiating payments, fetching transactions, performing account and balance checks, and generating risk reports.  # Root Cause Analysis  After a thorough investigation, it was found that the issue was triggered by a change which resulted in an impact on the service's stability which in turn degraded the performance of our AIS and PIS offerings.  # Remediation  Once the issue was identified, the change was immediately rolled back. This brought the affected service back to normal operation.  # Follow-up actions  To prevent similar issues in the future, Tink will be implementing the following actions:  1. Enhance the code review and internal testing process for the service in scope of the change.  2. Exposing changes to a smaller share of production traffic and gradually increasing the volume, allowing for a swifter rollback before issues become highly impacting.