Tink experienced a critical incident on May 22, 2025 affecting Payments and Settlement accounts and 1 more component, lasting 3h 12m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 22, 2025, 09:26 AM UTC
We are currently investigating an issue that is affecting several Tink products. See details for the full list of affected products.
- monitoring May 22, 2025, 09:34 AM UTC
Since 11:29 CEST all services started recovering and we are actively monitoring the situation.
- investigating May 22, 2025, 09:45 AM UTC
Services have partially recovered. We continue to investigate the issue. See details for the full list of affected products.
- monitoring May 22, 2025, 10:10 AM UTC
Services have recovered and we are actively monitoring the situation.
- resolved May 22, 2025, 12:38 PM UTC
The status has been stable since the last update and the incident is resolved. We apologize for the inconvenience.
- postmortem May 26, 2025, 11:31 AM UTC
# 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.