Is Tink Down Right Now? Check if there is a current outage ongoing.

We are currently investigating an issue that is affecting several Tink products, such as Income Check, Expense Check (Germany only) and Tink Console. See details for the full list of affected products.

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.

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.

The status has been stable since the last update and the incident is resolved. We apologize for the inconvenience.

Services have recovered and we are actively monitoring the situation.

Services have partially recovered. We continue to investigate the issue.See details for the full list of affected products.

Since 11:29 CEST all services started recovering and we are actively monitoring the situation.

We are currently investigating an issue that is affecting several Tink products.See details for the full list of affected products.

# Introduction  On 22nd May between 11:15 AM and 12:10 CEST Tink experienced a technical issue which impacted all AIS and PIS products on the European markets. During the time of the incident, end-users were experiencing issues with initiating payments, performing account checks and generating Risk reports.  # Root Cause Analysis  After conducting a thorough investigation, we discovered that the root cause was tied to a recent change, which increased the load on our internal infrastructure, which inadvertently led to this incident.  # Remediation  Once the scheduled job that caused the capacity issue was stopped, the affected service was able to self-recover, allowing Tink products to become available again.  # Follow-up actions  To prevent similar issues in the future Tink will be implementing the following actions:  1. Review the capacity of affected internal services and based on the results from the review, take appropriate actions.  2. Review and enhance our monitoring and alerts for the affected service.

The status has been stable since the last update and the incident is resolved. We apologize for the inconvenience.

Services have recovered and we are actively monitoring the situation.

Services have partially recovered. We continue to investigate the issue. See details for the full list of affected products.

Since 11:29 CEST all services started recovering and we are actively monitoring the situation.

We are currently investigating an issue that is affecting several Tink products. See details for the full list of affected products.

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

We are currently experiencing degraded performance for Settlement Accounts caused by a 3rd party vendor.

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

We are currently experiencing degraded performance for Settlement Accounts caused by a 3rd party vendor.

We experienced a technical issue between 11:46 and 11:53 CEST. During this time users were experiencing issues with using all Tink products. Performance has since returned to normal. We apologize for the inconvenience.

**Introduction**  On April 17, 2025, between 11:12 and 11:23 CET Tink experienced a technical issue which impacted Payments in multiple markets. During the time of the incident, end-users experienced issues in the step where to select their bank \(bank selection\).  ‌ **Root Cause Analysis**  After a thorough investigation, it was found that a configuration mismatch caused empty bank selection screens for end users in multiple markets.  ‌ **Remediation**  Once the issue was identified, the affected configuration was corrected.  ‌ **Follow-up actions**  To prevent similar issues in the future Tink will be implementing the following actions:  1. Add automatic checks on bank selection data sources to block empty configurations  1. Improve verification of bank selection configurations

Between 10:54 CET and 11:23 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.

We experienced degraded performance between 15:10 and 15:46 CET. During this period, some calls to the user/create and user/profiles endpoints were unsuccessful. Performance has since returned to normal. We apologize for the inconvenience.

## Introduction  On two separate occasions – on 14th April between 13:04 and 13:12 CEST and on 15th April between 04:00 and 04:11 CEST, Tink experienced a technical issue which impacted all AIS and PIS products for all European markets. During the time of the incident, end-users were experiencing issues with successfully completing Tink Link flows affecting Payment Initiation, Account Check and generating Risk reports. ## Root Cause Analysis  After a thorough investigation, it was found out that the issue was caused by a brief network issue in our cluster causing a temporary disruption in the provisioning of services responsible for the operation of our products.  ## Remediation  Once the issue was identified, we isolated the fault and ensured the network stability was fully restored.  ## Follow-up actions  To prevent similar issues in the future Tink will be implementing the following actions:  1. Permanently correct the node configuration of our virtualization cluster 2. Carry out additional testing to identify resiliency deficiencies

We experienced a technical issue between 13:04 CEST and 13:12 CEST. The issue caused a brief unavailability of all Tink products Performance has since returned to normal. We apologize for the inconvenience.

We experienced a technical issue between 04:10 CEST and 04:17 CEST. During the timeframe the Payment Initiation was not available. Performance has since returned to normal. We apologize for the inconvenience.

We experienced a technical issue between 12:12 CET and 12:22 CET that caused a degraded performance of all Tink porducts. Performance has since returned to normal. We apologize for the inconvenience.

**Introduction**  On March 6th 2025 between 10:50 and 11:16 CET Tink experienced a technical issue which impacted all Tink products in all markets. During the time of the incident, end-users were experiencing issues with payments and account refreshes, with slower responses and timeouts.  ‌ **Root Cause Analysis**  After a thorough investigation, it was found out that the issue had been caused by an automation to delete expired sessions executing too many requests in parallel which resulted in timeouts/failures to acquire connections for incoming requests    **Remediation**  The issue was resolved automatically when all accumulated deletion requests were processed.    **Follow-up actions**  To prevent similar issues in the future Tink will be implementing the following actions:  1. Improve alerting to detect case when delete jobs is queuing up  2. Improve robustness of session clean-ups to batch deletion of jobs

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

We are currently investigating an issue with Tink Link affecting all products on all markets.

We monitored the situation for a few more hours and we now consider the issue resolved.

Between 14:24 and 14:30 Tink experienced a quick technical glitch that caused degraded performance for Payments and other AIS products. Since then the issue was resolved. We are sorry for any inconvenience this has caused.

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

We are currently experiencing a delay to outbound Euro payments being processed.

We experienced degraded performance on February 27, 2025, between 21:05 and 21:15 CET. During this period some account information refreshes and payments may have failed. Performance has since returned to normal. We apologize for the inconvenience.

We experienced Degraded performance between 16:05 and 16:11 CET. During this period some aggregations and payments may have failed Performance has since returned to normal. We apologize for the inconvenience.

The issue has been resolved around 13:01 CET. We apologize for the inconvenience.

We are currently investigating an issue with the Income Check product, it is experiencing a degraded performance. All markets are probably affected.

We experienced a brief issue with Payment initiation between 09:45 AM and 09:52 AM CET. During that time, we observed an increased volume of cancelled Payment requests which led to a decrease in Tink Link success rate. The service has since returned to normal. We apologize for the inconvenience.

We experienced an outage to Tink Console today between 10:26 - 10:38 CET. Status has since returned to normal. We apologize for the inconvenience.

Introduction  On January 27 between 16:05 and 16:14 CET Tink experienced a technical issue impacting all AIS and PIS services in the EU and UK. During the time of the incident, end-users were experiencing disruptions due to a performance issue with a database.  ‌ Root Cause Analysis  Following a thorough investigation, it was determined that the issue was caused by a combination of events impacting the database performance, which subsequently necessitated a database restart to resolve the issue.  ‌ Remediation  The database automatically restarted, which successfully resolved the problem.  ‌ Follow-up actions  To prevent similar issues in the future Tink will be implementing the following actions:  1. Enhance the capacity of the impacted database by migrating it to a larger instance to improve robustness  1. Enhance our database monitoring and alerting

We have resolved the underlying issues. Impact lasted between 16:05 and 16:12 CET. We apologize for any problems this issue has caused.

We have identified an issue that is affecting multiple Tink products. We are actively working on resolving that issue.

## Introduction  On 20th January between 06:02 and 06:11 CET Tink experienced a technical issue which impacted Payments and Account Check Products for the European market. During the time of the incident, end-users and customers were experiencing issues with initiating payments and carrying out Account Checks.  ## Root Cause Analysis  After a thorough investigation, it was found out that Tink’s service used to connect to banks \(via use of eIDAS certificates\) experienced a brief connectivity issue, leading to the product degradation.  ## Remediation  The recovery process worked as designed and the issue self-healed.  ## Follow-up actions  To prevent similar issues in the future Tink will be implementing the following actions:  1. Continue to improve platform resiliency by upgrading selected internal services  2. Carry out a table-top exercise to simulate this scenario to investigate potential ways to shorten the self-recovery time. 

We experienced a drop in Tink Link success rate between 06:02 and 06:08 CET. Due to this issue, all of our products were briefly unavailable or showed temporary performance issues. The availability has since returned to normal. We apologize for the inconvenience.

**Introduction** On January 14 2025, between 10:17 and 12:33 CET, Tink experienced a technical issue which impacted Webhooks v2 delivery. During the time of the incident, Webhook events were not sent, causing different issues depending on how Webhook V2 events have been integrated in customer platforms. The following Webhook events were not sent during the time of the incident. * account-booked-transactions:modified * account-transactions:deleted * account:updated * account-transactions:modified * payment:updated * refresh:finished Webhook v1 events were not affected during the incident. ‌ **Root Cause Analysis** After a thorough investigation, it was found that a configuration change caused the validation of Webhook subscriptions to fail and Webhook events not being sent. ‌ **Remediation** Once the issue was identified, the change was reverted and the issue resolved. ‌ **Follow-up actions** To prevent similar issues in the future Tink will be implementing the following actions: 1. Strengthening our regression test suite to cover this specific configuration and to increase our general test coverage. 2. Strengthening our monitoring by adding more granular alerts per Webhook configuration segment.

Between 10:17 and 12:33 CET Tink has experienced an issue that impacted our ability to send v2 events. We have pinpointed the root cause of the issue and resolved it. We are sorry any issues this may have caused.

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

We have identified the cause of the issue and are working on a solution.

This incident has been resolved.

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

We experienced an issue with the credentials endpoint between 19:15 and 20:15 CEST. This resulted in increased latency on the create credentials API. Performance has since returned to normal. We apologise for any inconvenience caused.

Since 11:33 CET the situation has returned to normal. All impacted products are working as expected now. We are sorry for the inconvenience this issue has caused.

Since 11:13 CET Tink is experiencing an issue that is causing degraded performance for multiple products. We are actively working on resolving the issue.

We experienced an issue between 02:56 CET and 03:02 CET. during this time frame ~1295 on demand refreshes failed. Performance has since returned to normal. We apologize for the inconvenience.

Between 10:25-10:40 CET Tink experienced a technical issue that caused degraded performance for the Payments service on the German market. Since then the underlying issue was resolved and performance has returned to expected state. We are sorry for any inconvenience this issue has caused.

We experienced a small drop in success rates on October 22nd, 2024, between 11:05 and 14:48 CEST. During this time, there were minor disruptions with account and transaction aggregation. Performance has since returned to normal. We apologize for the inconvenience.

We experienced a small drop in success rates on November 6th, 2024, between 14:10 and 14:15 CET. During that time, there was a degraded performance for several products. Performance has since returned to normal. We apologize for the inconvenience.

We experienced a temporary issue between 10:19 CET and 10:24 CET. During that time, there was a degraded performance of Payments product. The performance has since returned to normal. We apologize for the inconvenience.

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

We are currently looking into an issue with degraded Continuous Access Refreshes performance in Swedish, Finnish and German markets.

Due to circumstances beyond Tink control, our cloud provider had experienced issues with processing requests, which may have caused a reduction of analytical events' availability for Tink Console. The vendor has since addressed the issues, returning full functionality to the analytics service. The service was affected between approximately 14:00 and 16:00 CEST. We apologize for the inconvenience.

We experienced a brief issue between 11:55 CEST and 12:03 CEST. During that time frame users may have experienced intermittent latency or availability issues with the affected products. Performance has since returned to normal. We apologize for the inconvenience.

We experienced degraded performance between 09:24 and 09:25 CEST today. This led to a slight drop in success rates for multiple products. Performance has since returned to normal. We apologize for the inconvenience.

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

We are investigating an issue with the Transaction Report Service. Currently, we are unable to generate reports.

We experienced an issue with the credentials endpoint between 10:18 and 10:23 CEST. In this time frame, the success rate was low. Performance/Status has since returned to normal. We apologize for the inconvenience.

#### **Introduction** On 2024-09-11 between 14:07 CEST and 14:13 CEST Tink experienced a technical issue, which impacted the following products: Payments, Money Manager, Account Check, Transactions, Income Check, Risk Insights and Expense Check. During the time of the incident end-users were experiencing issues with availability of the mentioned products. **Root Cause Analysis** After a thorough investigation, it was discovered that a scaling issue in our underlying infrastructure led to internal services becoming unavailable. During this period customers would have experienced timeouts or errors when iterating with the services.  **Remediation** The issue self healed as Auto-Scaling adjusted to meet demand and load was distributed across the cluster #### **Follow-up actions** To prevent similar issues in the future Tink will be implementing the following actions: 1. Review service and node resource limits within the infrastructure to avoid resource contention in future  2. Add additional metrics to identify and alert on areas of resource contention.

This issue has been resolved. 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.

We experienced availability issues for Expense Check product between 14:15 CEST and 15:20 CEST. During that time, Expense Check product was unavailable and generation of reports was not possible. The availability has since returned to normal. We apologize for the inconvenience.

This issue is now resolved.

We have received information from the certificate provider that they have resolved the issue on their side. Tink is closely monitoring the situation, however we already see improvement on our side as well and we are reenabling connections to the affected banks.

Due to an issue with a third party certificate provider, Tink is observing increased amount of errors when connecting to multiple banks. Tink is communicating these bank connectivity issues via their dedicated market StatusPages. Tink has escalated the issue to the vendor who is working on the issue.

We experienced a small drop in success rates for refreshes between 10:33 and 10:35. Some bank refreshes and authentications may have failed during this time. Performance has since returned to normal. We apologize for the inconvenience.

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

The upload of TPP secrets is currently not possible. Instead you might receive a 500 response. The situation is currently recovering though.

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

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

We are currently investigating an issue with Payments for all markets.

We experienced a temporary network issue between 08:44 AM and 08:59 AM CEST. During that time, the availability of Payments product was affected. The performance has since returned to normal. We apologize for the inconvenience.

We experienced a spike of errors on our platform between 14:32 and 14:38 CEST. During that time, the affected Products experienced increased latency and intermittent availability issues. The performance has since returned to normal. We apologize for the inconvenience.

#### **Introduction** On 5th June between 14:21 and 14:29 CEST Tink experienced a technical issue which impacted the availability of all products across all markets. During the time of the incident, customers would have been unable to access Tink’s APIs. **Root Cause Analysis** After a thorough investigation, it was found that a planned change to perform annual SSL certificate renewal was incorrectly implemented. As part of the import process the certificate chain was inadvertently altered causing a validation error upon the certificates. This impacted access to all services.    **Remediation** Once the issue was identified, the change was quickly rolled back, restoring the availability of our Products back to normal. #### **Follow-up actions** To prevent similar issues in the future Tink will be implementing the following actions: 1. Increase level of automation and validation for certificate renewal 2. Increase gradual rollout capabilities for certificate renewal

Tink has experienced a brief issue for a portion of customers, during a scheduled certificate rotation between 14:21 CEST and 14:29 CEST. During the timeframe multiple products were unavailable. Performance has since returned to normal. We apologize for the inconvenience.

#### **Introduction** On May 29th 2024 between 03:11 AM and 03:40 CEST Tink experienced a technical issue which impacted Payments in all markets. During the time of the incident, end-users were experiencing issues while performing Strong Customer Authentication for Payments. #### **Root Cause Analysis** After a thorough investigation, it was found that congestion of requests, in the service establishing connections to banks, caused latency in the platform. The congestion was caused by an abnormal traffic pattern in combination with an inefficient retry mechanism. The queued requests caused increased latency impacting Strong Customer Authentication for Payments. #### **Remediation** Once the issue was identified, the queue handling for connecting to banks was reset, and requests causing increased latencies aborted. #### **Follow-up actions** To prevent similar issues in the future Tink will be implementing the following actions: 1. Adjust the timeout and retry mechanism in the platform to prevent congestion 2. Improve logging in the retry mechanism

We experienced a degraded performance of Payments product between 03:11AM and 03:40AM. During that period, our customers may have experienced latency when attempting to initiate payments. The performance has since returned to normal. We apologize for the inconvenience.

We experienced degraded performance between 10:02 and 10:08 CET. This latency affected all products. Performance has since returned to normal. We apologize for the inconvenience.

This incident has been resolved.

The oauth/token endpoint will fail with 415 error code when content type is not specified. The issue has been identified and we are currently working on a solution.

We experienced an issue with Risk Decisioning today between 10:10 and 17:50 CEST. For successful Income Check reports users were not visible under Risk Decisioning view in Tink Console. For successful Income Check report using Income Check Bundles, the reports were not visible under Risk Decisioning view in Tink Console. Status has since returned to normal. We apologize for the inconvenience.

This incident has been resolved.

We are currently investigating an issue with Payments in TinkLink demo

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

We experiencing a slight drop of success rates on the creating of credentials.