Tink incident

Issue with multiple products

Minor Resolved View vendor source →

Tink experienced a minor incident on November 20, 2025 affecting Payments and Settlement accounts and 1 more component, lasting 4h 28m. The incident has been resolved; the full update timeline is below.

Started
Nov 20, 2025, 11:09 AM UTC
Resolved
Nov 20, 2025, 03:37 PM UTC
Duration
4h 28m
Detected by Pingoru
Nov 20, 2025, 11:09 AM UTC

Affected components

PaymentsSettlement accountsAccount CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense Check

Update timeline

  1. investigating Nov 20, 2025, 11:09 AM UTC

    We are currently investigating an issue with multiple products affecting all markets.

  2. monitoring Nov 20, 2025, 11:34 AM UTC

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

  3. resolved Nov 20, 2025, 03:37 PM UTC

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

  4. postmortem Nov 26, 2025, 02:36 PM UTC

    # 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.