Historique des pannes de Tink

1. 16 juillet 2026 à 08:17 UTCinvestigating

   Nous enquêtons actuellement sur une question qui touche plusieurs produits Tink. Voir la liste complète des produits concernés.

2. 16 juillet 2026 à 08:42 UTCidentified

   Le problème a été identifié et nous travaillons actuellement à une solution.

3. 16 juillet 2026 à 08:55 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

4. 16 juillet 2026 à 09:11 UTCmonitoring

   Le service se rétablit actuellement et nous suivons activement la situation.

5. 20 juillet 2026 à 12:47 UTCresolved

   Cette question a été résolue. Nous nous excusons pour le désagrément.

6. 22 juillet 2026 à 13:26 UTCpostmortem

   Présentation Le 16 juillet entre 09:54 et 10:56 CEST Tink a connu un problème technique qui a touché Tink Console, Tink Link, Payment Initiation Services, Account Information Services et certains produits à risque pour tous les marchés européens. Au moment de l'incident, les utilisateurs finals éprouvaient des problèmes avec le début ou l'achèvement des voyages d'authentification, de consentement, d'information sur les comptes et d'initiation au paiement, et n'étaient pas en mesure de se connecter à Tink Console pour gérer leurs intégrations avec la plateforme Tink. Analyse des causes profondes Après une enquête approfondie, il a été constaté qu'une dépendance à l'égard de l'infrastructure externe fournie par le fournisseur de services cloud de Tink, utilisé pour le routage du trafic orienté vers le client, avait entraîné l'interruption des trajets des utilisateurs basés sur Tink Link et l'indisponibilité temporaire de l'accès à Tink Console pour certains clients. Réparation Une fois le problème identifié, Tink a acheminé le trafic affecté par une autre configuration et a rétabli les services touchés à une exploitation normale. Actions de suivi Pour éviter des problèmes similaires à l'avenir, Tink mettra en œuvre les actions suivantes: 1. Améliorer la surveillance et l'alerte des dépendances essentielles en matière d'infrastructure externe. 2. Documenter et valider les procédures de récupération pour le routage autour de défaillances similaires. 3. Exécuter une formation supplémentaire pour identifier et traiter plus rapidement des problèmes d ' infrastructure comparables.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juillet 2026 à 13:39 UTCinvestigating

   Nous enquêtons actuellement sur une question qui touche plusieurs produits Tink. Voir la liste complète des produits concernés.

2. 7 juillet 2026 à 13:54 UTCmonitoring

   Le service se rétablit actuellement et nous suivons activement la situation.

3. 8 juillet 2026 à 13:37 UTCresolved

   Cette question a été résolue. Nous nous excusons pour le désagrément.

4. 9 juillet 2026 à 14:31 UTCpostmortem

   **Introduction** Le 2026-07-07 entre 15:26 et 15:51 CEST, Tink a connu un problème technique qui a affecté la disponibilité de l'API pour certains de nos clients. Au cours de l'incident, les utilisateurs finaux ont éprouvé des problèmes avec l'accès aux services Tink touchés. **Analyse des causes des blessures** Après une enquête approfondie, l'événement qui a déclenché le problème temporaire de disponibilité de l'API a été identifié et réglé avec succès. **Réparation** Une fois le problème identifié, Tink a rétabli la disponibilité des services et mis en place des mesures de protection supplémentaires pour améliorer la résilience face à des événements semblables. **Mesures de suivi** Pour éviter des problèmes similaires à l'avenir, Tink mettra en œuvre les actions suivantes: 1. Renforcer les contrôles de protection dans les environnements de production pertinents. 2. Améliorer les procédures de suivi et d ' intervention pour les manifestations à haut impact. 3. Examiner et améliorer la résilience des services afin de réduire l ' impact d ' incidents similaires.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 22 juin 2026 à 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 juin 2026 à 10:15 UTCidentified

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

2. 16 juin 2026 à 11:32 UTCresolved

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

1. 2 juin 2026 à 09:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2 juin 2026 à 10:25 UTCmonitoring

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

3. 3 juin 2026 à 08:31 UTCresolved

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

1. 1 juin 2026 à 00:35 UTCidentified

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

2. 1 juin 2026 à 04:53 UTCresolved

   This incident has been resolved.

1. 28 mai 2026 à 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 à 18:02 UTCresolved

   This incident has been resolved.

1. 21 mai 2026 à 21:52 UTCinvestigating

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

2. 21 mai 2026 à 22:47 UTCresolved

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

1. 19 mai 2026 à 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 à 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 à 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 à 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 à 14:19 UTCresolved

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

1. 25 mars 2026 à 09:15 UTCinvestigating

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

2. 25 mars 2026 à 10:04 UTCresolved

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

1. 19 mars 2026 à 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 mars 2026 à 08:12 UTCresolved

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

1. 5 mars 2026 à 09:48 UTCinvestigating

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

2. 5 mars 2026 à 10:19 UTCresolved

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

3. 10 mars 2026 à 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 mars 2026 à 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 février 2026 à 15:53 UTCinvestigating

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

2. 4 février 2026 à 08:09 UTCresolved

   This incident has been resolved.

1. 3 février 2026 à 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 février 2026 à 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 février 2026 à 18:17 UTCresolved

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

3. 5 février 2026 à 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 janvier 2026 à 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 janvier 2026 à 09:47 UTCresolved

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

1. 8 décembre 2025 à 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 à 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 à 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