Istoricul incidentelor Tink

1. 16 iulie 2026 la 08:17 UTCinvestigating

   Investigăm în prezent o problemă care afectează mai multe produse Tink. Vezi detalii pentru lista completă a produselor afectate.

2. 16 iulie 2026 la 08:42 UTCidentified

   Problema a fost identificată și lucrăm în prezent la o soluție.

3. 16 iulie 2026 la 08:55 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

4. 16 iulie 2026 la 09:11 UTCmonitoring

   Serviciul se recuperează în prezent și monitorizăm în mod activ situația.

5. 20 iulie 2026 la 12:47 UTCresolved

   Această problemă a fost rezolvată. Ne cerem scuze pentru deranj.

6. 22 iulie 2026 la 13:26 UTCpostmortem

   ## Introducere Pe 16 iulie intre 09:54 si 10:56 CEST Tink s-a confruntat cu o problemă tehnică care a afectat Tink Console, Tink Link, Servicii de inițiere a plăților, Servicii de informare a conturilor și produse de risc selectate pentru toate piețele europene. În timpul incidentului, utilizatorii finali s-au confruntat cu probleme legate de începerea sau completarea autentificării, consimțământul, informarea contului și călătoriile de plată și nu s-au putut conecta la Tink Console pentru a-și gestiona integrarea cu platforma Tink. ## Root Cause Analysis După o investigație aprofundată, s-a constatat că o dependență externă de infrastructură oferită de furnizorul de cloud Tink ## Remediation Odată ce problema a fost identificată, Tink rutat afectat traficul printr-o configurație alternativă și a restaurat serviciile afectate la funcționarea normală. ♪ Acțiuni de urmărire Pentru a preveni chestiuni similare în viitor, Tink va implementa următoarele acțiuni: 1. Îmbunătățirea monitorizării și alertei pentru dependențele critice de infrastructură externă. 2. Documentele și validarea procedurilor de recuperare pentru rutarea în jurul unor eșecuri similare. 3. Să efectueze o formare suplimentară pentru identificarea și gestionarea mai rapidă a problemelor comparabile legate de infrastructură.

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 13:39 UTCinvestigating

   Investigăm în prezent o problemă care afectează mai multe produse Tink. Vezi detalii pentru lista completă a produselor afectate.

2. 7 iulie 2026 la 13:54 UTCmonitoring

   Serviciul se recuperează în prezent și monitorizăm în mod activ situația.

3. 8 iulie 2026 la 13:37 UTCresolved

   Această problemă a fost rezolvată. Ne cerem scuze pentru deranj.

4. 9 iulie 2026 la 14:31 UTCpostmortem

   ** Introducţie ** La 2026-07-07 între 15:26 și 15:51 CEST, Tink a experimentat o problemă tehnică care a afectat API disponibilitatea pentru unii dintre clienții noștri. În timpul incidentului, utilizatorii finali au avut probleme cu accesarea serviciilor Tink afectate. **Root Cause Analysis** După o anchetă aprofundată, evenimentul care a declanșat problema disponibilității temporare a API a fost identificat și abordat cu succes. ** Remediation ** Odată ce problema a fost identificată, Tink a restabilit disponibilitatea serviciului și a pus în aplicare măsuri suplimentare de protecție pentru a îmbunătăți rezistența la evenimente similare. **Follow-up actions** Pentru a preveni chestiuni similare în viitor, Tink va implementa următoarele acțiuni: 1. Consolidarea controalelor de protecție în mediile de producție relevante. 2. Îmbunătățirea procedurilor de monitorizare și de răspuns pentru evenimente de disponibilitate cu impact ridicat. 3. Revizuirea și consolidarea rezilienței serviciilor în vederea reducerii impactului unor incidente similare.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iunie 2026 la 15:13 UTCresolved

   Between June 20th, 02:00 CEST and June 22nd, 13:40 CET Tink has experienced degraded performance with webhooks. We have pinpointed the root cause of the issue and resolved it. We are sorry any issues this may have caused.

1. 16 iunie 2026 la 10:15 UTCidentified

   The issue has been identified and we are currently working on a solution.

2. 16 iunie 2026 la 11:32 UTCresolved

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

1. 2 iunie 2026 la 09:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2 iunie 2026 la 10:25 UTCmonitoring

   Service is currently recovering and we are actively monitoring the situation.

3. 3 iunie 2026 la 08:31 UTCresolved

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

1. 1 iunie 2026 la 00:35 UTCidentified

   The issue has been identified and we are currently working on a solution.

2. 1 iunie 2026 la 04:53 UTCresolved

   This incident has been resolved.

1. 28 mai 2026 la 16:47 UTCidentified

   We have identified and are currently investigating an issue with our provider which is affecting inbound Faster Payments Service (FPS), which may result in delays.

2. 28 mai 2026 la 18:02 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 la 21:52 UTCinvestigating

   We are currently investigating an issue with payments in German market.

2. 21 mai 2026 la 22:47 UTCresolved

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

1. 19 mai 2026 la 09:53 UTCinvestigating

   We have identified and are currently investigating an issue with our provider which is affecting both outbound and inbound SEPA payments, which may result in delays.

2. 21 mai 2026 la 13:29 UTCmonitoring

   We continue to monitor an issue affecting both outbound and inbound SEPA payments. While some payments are processing, we cannot yet confirm full service restoration. We are actively investigating and will provide a further update as soon as possible. We apologise for the inconvenience.

3. 22 mai 2026 la 07:39 UTCresolved

   We can confirm that the previously identified issue affecting inbound and outbound SEPA payments has now been resolved. Payments are processing as expected. We apologise for the inconvenience caused and thank you for your patience.

1. 11 mai 2026 la 13:32 UTCinvestigating

   We are currently investigating an issue with the account exclusion functionality, as accounts are not being excluded as intended. Further updates will be provided as soon as possible.

2. 11 mai 2026 la 14:19 UTCresolved

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

1. 25 martie 2026 la 09:15 UTCinvestigating

   We are currently investigating an issue with Bulk Payments in Sweden.

2. 25 martie 2026 la 10:04 UTCresolved

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

1. 19 martie 2026 la 21:16 UTCinvestigating

   We are currently looking into an issue with Nordea bulk payments. The initiation for the SE market has been failing for about 3 hours.

2. 20 martie 2026 la 08:12 UTCresolved

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

1. 5 martie 2026 la 09:48 UTCinvestigating

   We are currently investigating an issue with Payment initiations across multiple markets.

2. 5 martie 2026 la 10:19 UTCresolved

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

3. 10 martie 2026 la 11:34 UTCpostmortem

   **Introduction**  On 5 March, between 10:31 CET and 10:59 CET, Tink experienced a technical issue that impacted the Payment Initiation service across multiple markets. The issue was detected immediately, and mitigation actions were taken promptly to limit the impact. During the incident window, some end users experienced difficulties when initiating payments.  **Root Cause Analysis**  Following a thorough investigation, it was determined that a recently introduced change contained a defect that caused unexpected request failures within the Payment Initiation service. This resulted in a temporary disruption to payment initiation flows in the affected markets.  **Remediation**  As soon as the issue was identified, the affected deployment was immediately rolled back. This action mitigated the impact and restored normal service functionality.  **Follow-up actions**  To reduce the risk of similar incidents in the future, Tink is taking the following actions:  1. **Extend test coverage for payment initiation scenarios** Further strengthen the pre-deployment validation for payment flows by expanding our end-to-end test coverage for payment flows.

1. 3 martie 2026 la 13:03 UTCresolved

   We experienced a technical issue between 2 March 11:30 CET and 3 March 13:42 CET that caused degraded performance of Transactions and Risk reporting. During this time, some users may have experienced empty reports or missing data when viewing or downloading Transactions and Risk reports. Performance has since returned to normal. We apologize for the inconvenience.

1. 3 februarie 2026 la 15:53 UTCinvestigating

   We are currently investigating an issue with Analytics in Tink Console.

2. 4 februarie 2026 la 08:09 UTCresolved

   This incident has been resolved.

1. 3 februarie 2026 la 10:42 UTCresolved

   We experienced a technical issue between 10:43 CET and 11:18 CET that caused a degraded performance of the Payment product. During this time some users in the FI and DE markets may have experienced issues with initiating payments. Performance has since returned to normal. We apologize for the inconvenience.

1. 2 februarie 2026 la 17:15 UTCinvestigating

   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.

2. 2 februarie 2026 la 18:17 UTCresolved

   This issue has been resolved as of 19:01 CET. We apologize for the inconvenience.

3. 5 februarie 2026 la 14:21 UTCpostmortem

   # 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

1. 21 ianuarie 2026 la 09:33 UTCinvestigating

   We’re currently experiencing degraded performance affecting multiple products since 10:01 CET. Some users may encounter issues with availability.

2. 21 ianuarie 2026 la 09:47 UTCresolved

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

1. 8 decembrie 2025 la 10:14 UTCresolved

   We experienced Temporary outage on data enrichment service between 10.20 and 10:40 CET This resulted in increased of Http 503 responses. Performance has since returned to normal. We apologise for the inconvenience.

1. 24 noiembrie 2025 la 14:29 UTCresolved

   We experienced a technical issue between 15:06 CET and 15:24 CET. During this time users had issues with availability of Tink products. Status has since returned to normal. We apologise for the inconvenience.

2. 26 noiembrie 2025 la 15:50 UTCpostmortem

   # 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