Tink outage history

We have experienced an outage with Payment Initiation and Account check servicices between 18:15 and 19:35 CET in Autria , Germany, Poland and Czech Republic Performance has since returned to normal. We apologize for the inconvenience.

We are currently experiencing delays in returning enriched transactions. Transaction ingestion is operating as expected.

This incident has been resolved.

We apologise for the inconvenience caused. On 6 October 2026, between 09:30 CEST and 14:30 CEST, we experienced a temporary issue that resulted in delays in enrichment processing for the Data Enrichment API. The issue has now been resolved, and enrichment processing is operating normally.

We experienced a temporary outage between 15:28 CEST and 16:49 CEST. This resulted in increased of 503 responses. Performance has since returned to normal. We apologise for the inconvenience.

We are currently investigating an issue with Payment Initiation.

We are monitoring post recovery.

Service is back to normal.

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

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

We are continuing to work on a fix for this issue.

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

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

## Introduction  On 16th July between 09:54 and 10:56 CEST Tink experienced a technical issue which impacted Tink Console, Tink Link, Payment Initiation Services, Account Information Services, and selected risk products for all European markets. During the time of the incident, end-users were experiencing issues with starting or completing authentication, consent, account-information, and payment-initiation journeys, and were unable to log in to Tink Console to manage their integrations with Tink platform.  ## Root Cause Analysis  After a thorough investigation, it was found out that an external infrastructure dependency provided by Tink’s cloud provider used for routing customer-facing traffic malfunctioned, which led to interruption of Tink Link-based user journeys and temporary unavailability of Tink Console access for some customers.  ## Remediation  Once the issue was identified, Tink routed affected traffic through an alternative configuration and restored the impacted services to normal operation.  ## Follow-up actions  To prevent similar issues in the future, Tink will be implementing the following actions:  1. Improve monitoring and alerting for critical external infrastructure dependencies.  2. Document and validate recovery procedures for routing around similar failures.  3. Run additional training for faster identification and handling of comparable infrastructure-related issues.

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

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

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

**Introduction**  On 2026-07-07 between 15:26 and 15:51 CEST, Tink experienced a technical issue which impacted API availability for some of our customers. During the incident, end-users experienced issues with accessing affected Tink services.  **Root Cause Analysis**  After a thorough investigation, the event which triggered the temporary API availability issue was identified and successfully addressed.  **Remediation**  Once the issue was identified, Tink restored service availability and implemented additional protective measures to improve resilience against similar events.  **Follow-up Actions**  To prevent similar issues in the future, Tink will be implementing the following actions:  1. Strengthen protective controls across relevant production environments.  2. Improve monitoring and response procedures for high-impact availability events.  3. Review and enhance service resilience to reduce the impact of similar incidents.

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.