Cronologia delle interruzioni di Tink

1. 16 luglio 2026 alle ore 08:17 UTCinvestigating

   Stiamo attualmente indagando su un problema che riguarda diversi prodotti Tink. Vedi i dettagli per l'elenco completo dei prodotti interessati.

2. 16 luglio 2026 alle ore 08:42 UTCidentified

   Il problema è stato identificato e stiamo attualmente lavorando a una soluzione.

3. 16 luglio 2026 alle ore 08:55 UTCidentified

   Stiamo continuando a lavorare per risolvere questo problema.

4. 16 luglio 2026 alle ore 09:11 UTCmonitoring

   Il servizio sta attualmente recuperando e stiamo monitorando attivamente la situazione.

5. 20 luglio 2026 alle ore 12:47 UTCresolved

   Questo problema è stato risolto. Ci scusiamo per l'inconveniente.

6. 22 luglio 2026 alle ore 13:26 UTCpostmortem

   ## Introduzione Il 16 luglio dalle 09:54 alle 10:56 Tink ha sperimentato un problema tecnico che ha colpito Tink Console, Tink Link, Payment Initiation Services, Account Information Services e prodotti di rischio selezionati per tutti i mercati europei. Durante il periodo dell'incidente, gli utenti finali stavano sperimentando problemi con l'avvio o il completamento di autenticazione, consenso, informazioni account e viaggi di pagamento-iniziazione, e non erano in grado di accedere a Tink Console per gestire le loro integrazioni con la piattaforma Tink. # Root Cause Analysis Dopo un'indagine approfondita, è stato scoperto che una dipendenza dalle infrastrutture esterne fornita dal provider cloud di Tink utilizzato per il routing del traffico rivolto al cliente malfunzionato, che ha portato all'interruzione dei viaggi utente basati su Tink Link e all'invalidità temporanea dell'accesso a Tink Console per alcuni clienti. ## Remediation Una volta individuato il problema, Tink ha instradato il traffico interessato attraverso una configurazione alternativa e ha ripristinato i servizi incisi al normale funzionamento. ## Azioni successive Per prevenire problemi simili in futuro, Tink sarà l'attuazione delle seguenti azioni: 1. Migliorare il monitoraggio e l'avviso per le dipendenze critiche delle infrastrutture esterne. 2. Documentare e convalidare le procedure di recupero per il routing intorno a guasti simili. 3. Eseguire una formazione aggiuntiva per l'identificazione e la gestione più rapida di problemi correlati alle infrastrutture.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 7 luglio 2026 alle ore 13:39 UTCinvestigating

   Stiamo attualmente indagando su un problema che riguarda diversi prodotti Tink. Vedi i dettagli per l'elenco completo dei prodotti interessati.

2. 7 luglio 2026 alle ore 13:54 UTCmonitoring

   Il servizio sta attualmente recuperando e stiamo monitorando attivamente la situazione.

3. 8 luglio 2026 alle ore 13:37 UTCresolved

   Questo problema è stato risolto. Ci scusiamo per l'inconveniente.

4. 9 luglio 2026 alle ore 14:31 UTCpostmortem

   # Introduzione # Il 2026-07-07 tra 15:26 e 15:51 CEST, Tink ha sperimentato un problema tecnico che ha colpito la disponibilità API per alcuni dei nostri clienti. Durante l'incidente, gli utenti finali hanno riscontrato problemi con l'accesso ai servizi Tink colpiti. #Root Cause Analysis # Dopo un'indagine approfondita, l'evento che ha innescato il problema di disponibilità API temporanea è stato identificato e affrontato con successo. Revisione: Una volta individuato il problema, Tink ha ripristinato la disponibilità del servizio e ha implementato ulteriori misure di protezione per migliorare la resilienza contro eventi simili. **Azioni di base ** Per prevenire problemi simili in futuro, Tink sarà l'attuazione delle seguenti azioni: 1. Rafforzare i controlli protettivi in ambienti di produzione rilevanti. 2. Migliorare le procedure di monitoraggio e risposta per eventi di disponibilità ad alto impatto. 3. Review e migliorare la resilienza del servizio per ridurre l'impatto di incidenti simili.

Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.

1. 22 giugno 2026 alle ore 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 giugno 2026 alle ore 10:15 UTCidentified

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

2. 16 giugno 2026 alle ore 11:32 UTCresolved

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

1. 2 giugno 2026 alle ore 09:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2 giugno 2026 alle ore 10:25 UTCmonitoring

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

3. 3 giugno 2026 alle ore 08:31 UTCresolved

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

1. 1 giugno 2026 alle ore 00:35 UTCidentified

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

2. 1 giugno 2026 alle ore 04:53 UTCresolved

   This incident has been resolved.

1. 28 maggio 2026 alle ore 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 maggio 2026 alle ore 18:02 UTCresolved

   This incident has been resolved.

1. 21 maggio 2026 alle ore 21:52 UTCinvestigating

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

2. 21 maggio 2026 alle ore 22:47 UTCresolved

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

1. 19 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 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 maggio 2026 alle ore 14:19 UTCresolved

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

1. 25 marzo 2026 alle ore 09:15 UTCinvestigating

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

2. 25 marzo 2026 alle ore 10:04 UTCresolved

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

1. 19 marzo 2026 alle ore 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 marzo 2026 alle ore 08:12 UTCresolved

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

1. 5 marzo 2026 alle ore 09:48 UTCinvestigating

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

2. 5 marzo 2026 alle ore 10:19 UTCresolved

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

3. 10 marzo 2026 alle ore 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 marzo 2026 alle ore 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 febbraio 2026 alle ore 15:53 UTCinvestigating

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

2. 4 febbraio 2026 alle ore 08:09 UTCresolved

   This incident has been resolved.

1. 3 febbraio 2026 alle ore 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 febbraio 2026 alle ore 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 febbraio 2026 alle ore 18:17 UTCresolved

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

3. 5 febbraio 2026 alle ore 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 gennaio 2026 alle ore 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 gennaio 2026 alle ore 09:47 UTCresolved

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

1. 8 dicembre 2025 alle ore 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 novembre 2025 alle ore 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 novembre 2025 alle ore 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