Tink experienced a critical incident on February 2, 2026 affecting Payments, lasting 1h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 02, 2026, 05:15 PM UTC
We’re currently experiencing a major outage impacting Payments since 17:48 CET. Our team is investigating the issue, and we’ll share updates here as soon as possible.
- resolved Feb 02, 2026, 06:17 PM UTC
This issue has been resolved as of 19:01 CET. We apologize for the inconvenience.
- postmortem Feb 05, 2026, 02:21 PM UTC
# Introduction On 2 February 2026, between 17:48 and 19:01 CET, Tink experienced a technical issue that affected the availability of all Payments products across all markets. During this period of the incident, end‑users were unable to successfully initiate one‑time or bulk payments. # Root Cause Analysis Following a detailed investigation, it was determined that the incident was caused by an availability issue affecting a critical database table. As this table is a required dependency for multiple service flows, all flows relying on it were unable to function during the incident. # Remediation Once the issue was identified, a new copy of the database table was created to minimize the total duration of unavailability of our PIS \(Payment Initiation Service\) and restore normal service. # Follow-up actions To prevent similar issues in the future, Tink will be implementing the following actions: 1. Review alerting and improve monitoring of database table parameters