Resolved after 4 hours 28 minutes, affecting Payments and Settlement accounts and 1 more, on November 20, 2025.
# 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.
Affected components
Update timeline
- investigating Nov 20, 2025, 11:09 AM UTC
We are currently investigating an issue with multiple products affecting all markets.
- monitoring Nov 20, 2025, 11:34 AM UTC
Service is currently recovering and we are actively monitoring the situation.
- resolved Nov 20, 2025, 03:37 PM UTC
This issue has been resolved. We apologize for the inconvenience.
- 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.
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.