Historial de interrupciones de Tink

1. July 16, 2026 at 8:17 AM UTCinvestigating

   Actualmente estamos investigando un problema que está afectando varios productos Tink. Ver detalles para la lista completa de productos afectados.

2. July 16, 2026 at 8:42 AM UTCidentified

   La cuestión ha sido identificada y actualmente estamos trabajando en una solución.

3. July 16, 2026 at 8:55 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

4. July 16, 2026 at 9:11 AM UTCmonitoring

   El servicio se está recuperando y estamos monitoreando activamente la situación.

5. July 20, 2026 at 12:47 PM UTCresolved

   Esta cuestión se ha resuelto. Nos disculpamos por la molestia.

6. July 22, 2026 at 1:26 PM UTCpostmortem

   ## Introduction El 16 de julio entre las 09:54 y las 10:56 CEST Tink experimentó un problema técnico que impactó a Tink Console, Tink Link, Payment Initiation Services, Account Information Services, y algunos productos de riesgo para todos los mercados europeos. Durante el tiempo del incidente, los usuarios finales estaban experimentando problemas con iniciar o completar la autenticación, consentimiento, información de cuenta y viajes de iniciación de pagos, y no pudieron iniciar sesión en Tink Console para gestionar sus integraciones con la plataforma Tink. ## Root Cause Analysis Después de una investigación exhaustiva, se descubrió que una dependencia de infraestructura externa proporcionada por el proveedor de nube de Tink utilizaba para enrutar el tráfico de cara al cliente mal funcionado, lo que condujo a la interrupción de los viajes de usuarios basados en Tink Link y la falta temporal de acceso a Tink Console para algunos clientes. ## Remediation Una vez identificado el problema, Tink afectó el tráfico a través de una configuración alternativa y restauró los servicios impactados a la operación normal. ## Follow-up actions Para evitar problemas similares en el futuro, Tink implementará las siguientes acciones: 1. Mejorar la vigilancia y alerta de las dependencias críticas de infraestructura externa. 2. Documentar y validar los procedimientos de recuperación para el enrutamiento alrededor de fallas similares. 3. Realizar más capacitación para determinar y gestionar más rápidamente cuestiones comparables relacionadas con la infraestructura.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 7, 2026 at 1:39 PM UTCinvestigating

   Actualmente estamos investigando un problema que está afectando varios productos Tink. Ver detalles para la lista completa de productos afectados.

2. July 7, 2026 at 1:54 PM UTCmonitoring

   El servicio se está recuperando y estamos monitoreando activamente la situación.

3. July 8, 2026 at 1:37 PM UTCresolved

   Esta cuestión se ha resuelto. Nos disculpamos por la molestia.

4. July 9, 2026 at 2:31 PM UTCpostmortem

   **Introducción** En 2026-07-07 entre 15:26 y 15:51 CEST, Tink experimentó un problema técnico que impactó la disponibilidad de API para algunos de nuestros clientes. During the incident, end-users experienced issues with accessing affected Tink services. * Análisis de la causa real* Después de una investigación exhaustiva, se identificó y abordó con éxito el evento que desencadenó la cuestión de disponibilidad temporal de API. **Remediación** Una vez identificado el problema, Tink restableció la disponibilidad de servicios e implementó medidas de protección adicionales para mejorar la resiliencia contra eventos similares. ** Medidas complementarias** Para evitar problemas similares en el futuro, Tink implementará las siguientes acciones: 1. Fortalecer los controles de protección en los entornos de producción pertinentes. 2. Mejorar los procedimientos de vigilancia y respuesta para los actos de disponibilidad de alto impacto. 3. Examinar y aumentar la resiliencia de los servicios para reducir los efectos de incidentes similares.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 22, 2026 at 3:13 PM 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. June 16, 2026 at 10:15 AM UTCidentified

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

2. June 16, 2026 at 11:32 AM UTCresolved

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

1. June 2, 2026 at 9:45 AM UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. June 2, 2026 at 10:25 AM UTCmonitoring

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

3. June 3, 2026 at 8:31 AM UTCresolved

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

1. June 1, 2026 at 12:35 AM UTCidentified

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

2. June 1, 2026 at 4:53 AM UTCresolved

   This incident has been resolved.

1. May 28, 2026 at 4:47 PM 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. May 28, 2026 at 6:02 PM UTCresolved

   This incident has been resolved.

1. May 21, 2026 at 9:52 PM UTCinvestigating

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

2. May 21, 2026 at 10:47 PM UTCresolved

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

1. May 19, 2026 at 9:53 AM 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. May 21, 2026 at 1:29 PM 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. May 22, 2026 at 7:39 AM 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. May 11, 2026 at 1:32 PM 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. May 11, 2026 at 2:19 PM UTCresolved

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

1. March 25, 2026 at 9:15 AM UTCinvestigating

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

2. March 25, 2026 at 10:04 AM UTCresolved

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

1. March 19, 2026 at 9:16 PM 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. March 20, 2026 at 8:12 AM UTCresolved

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

1. March 5, 2026 at 9:48 AM UTCinvestigating

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

2. March 5, 2026 at 10:19 AM UTCresolved

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

3. March 10, 2026 at 11:34 AM 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. March 3, 2026 at 1:03 PM 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. February 3, 2026 at 3:53 PM UTCinvestigating

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

2. February 4, 2026 at 8:09 AM UTCresolved

   This incident has been resolved.

1. February 3, 2026 at 10:42 AM 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. February 2, 2026 at 5:15 PM 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. February 2, 2026 at 6:17 PM UTCresolved

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

3. February 5, 2026 at 2:21 PM 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. January 21, 2026 at 9:33 AM UTCinvestigating

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

2. January 21, 2026 at 9:47 AM UTCresolved

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

1. December 8, 2025 at 10:14 AM 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. November 24, 2025 at 2:29 PM 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. November 26, 2025 at 3:50 PM 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