Tink incident

Degraded performance of Tink Link affecting all products

Resolved after 15 minutes, affecting Payments and Settlement accounts and 1 more, on March 6, 2025.

postmortem Mar 11, 2025, 02:34 PM UTC

**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

Started
Mar 06, 2025, 10:18 AM UTC
Resolved
Mar 06, 2025, 10:34 AM UTC
Duration
15m
Detected by Pingoru
Mar 06, 2025, 10:18 AM UTC

Affected components

PaymentsSettlement accountsAccount CheckBalance CheckTransactionsBusiness Account CheckBusiness TransactionsIncome CheckRisk InsightsExpense Check

Update timeline

  1. investigating Mar 06, 2025, 10:18 AM UTC

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

  2. resolved Mar 06, 2025, 10:34 AM UTC

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

  3. postmortem Mar 11, 2025, 02:34 PM UTC

    **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

Your product runs on more than Tink

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →