Introduction

On 24th November between 15:06 and 15:30 CET Tink experienced a technical issue which impacted all products in all European markets. During the time of the incident, end-users were experiencing issues with initiating payments, fetching transactions, performing account and balance checks, generating risk reports.

Root Cause Analysis

After a thorough investigation, it was found that the issue was caused by an attempt to resume a failed backup job on our main production database. Initiating a command to verify data integrity caused a lock on the database.

Remediation

Once the issue was identified, the process which was causing the lock was terminated.

Follow-up actions

To prevent similar issues in the future, Tink will be implementing the following actions:

1. We are strengthening our internal processes so that any resource-intensive commands meant to be run on production databases should go through internal review with full risk assessment and run on replicas and/or non-production environments first