Histórico de interrupções do Tink

1. 16 Gouere 2026 da 08:17 UTCinvestigating

   Atualmente estamos investigando uma questão que está afetando vários produtos Tink. Veja detalhes para a lista completa de produtos afetados.

2. 16 Gouere 2026 da 08:42 UTCidentified

   A questão foi identificada e estamos actualmente a trabalhar numa solução.

3. 16 Gouere 2026 da 08:55 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

4. 16 Gouere 2026 da 09:11 UTCmonitoring

   O serviço está actualmente a recuperar e estamos a acompanhar activamente a situação.

5. 20 Gouere 2026 da 12:47 UTCresolved

   Esta questão foi resolvida. Pedimos desculpa pelo inconveniente.

6. 22 Gouere 2026 da 13:26 UTCpostmortem

   # # Introdução Em 16 de julho entre 09:54 e 10:56 CEST Tink teve um problema técnico que afetou Sink Console, Tink Link, Serviços de Iniciação de Pagamento, Serviços de Informação de Conta e produtos de risco selecionados para todos os mercados europeus. Durante o tempo do incidente, os usuários finais estavam tendo problemas com início ou conclusão de autenticação, consentimento, informações de conta e viagens de iniciação de pagamento, e não foram capazes de fazer login no Console Tink para gerenciar suas integrações com a plataforma Tink. # # Análise de Causas Raízes Após uma investigação aprofundada, descobriu-se que uma dependência de infraestrutura externa fornecida pelo provedor de nuvem da Tink usado para rotear o tráfego voltado para o cliente falhou, o que levou à interrupção das viagens de usuário baseadas no Tink Link e à indisponibilidade temporária do acesso ao Console da Tink para alguns clientes. # # Remediação Uma vez identificado o problema, o Tink roteou o tráfego por meio de uma configuração alternativa e restaurou os serviços impactados à operação normal. # # Acções de acompanhamento Para evitar problemas semelhantes no futuro, a Tink irá implementar as seguintes ações: 1. Melhorar o monitoramento e alerta para dependências críticas de infraestrutura externa. 2. Documentar e validar procedimentos de recuperação para roteamento em torno de falhas semelhantes. 3. Execute treinamento adicional para uma identificação e tratamento mais rápidos de problemas comparáveis relacionados à infraestrutura.

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Gouere 2026 da 13:39 UTCinvestigating

   Atualmente estamos investigando uma questão que está afetando vários produtos Tink. Veja detalhes para a lista completa de produtos afetados.

2. 7 Gouere 2026 da 13:54 UTCmonitoring

   O serviço está actualmente a recuperar e estamos a acompanhar activamente a situação.

3. 8 Gouere 2026 da 13:37 UTCresolved

   Esta questão foi resolvida. Pedimos desculpa pelo inconveniente.

4. 9 Gouere 2026 da 14:31 UTCpostmortem

   **Introdução Em 2026-07-07 entre 15:26 e 15:51 CEST, Tink experimentou um problema técnico que afetou a disponibilidade de API para alguns de nossos clientes. Durante o incidente, os usuários finais experimentaram problemas com o acesso aos serviços Tink afetados. ** Análise de Causas Root Após uma investigação minuciosa, o evento que desencadeou o problema temporário de disponibilidade da API foi identificado e abordado com sucesso. **Remediação** Uma vez identificada a questão, Tink restaurou a disponibilidade de serviços e implementou medidas de proteção adicionais para melhorar a resiliência contra eventos semelhantes. ** Acções de seguimento ** Para evitar problemas semelhantes no futuro, a Tink irá implementar as seguintes ações: 1. Fortalecer os controles de proteção em ambientes de produção relevantes. 2. Melhorar os procedimentos de monitoramento e resposta para eventos de disponibilidade de alto impacto. 3. Analisar e melhorar a resiliência dos serviços para reduzir o impacto de incidentes semelhantes.

Traduzido automaticamente da atualização oficial do incidente.

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

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

2. 16 Mezheven 2026 da 11:32 UTCresolved

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

1. 2 Mezheven 2026 da 09:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2 Mezheven 2026 da 10:25 UTCmonitoring

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

3. 3 Mezheven 2026 da 08:31 UTCresolved

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

1. 1 Mezheven 2026 da 00:35 UTCidentified

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

2. 1 Mezheven 2026 da 04:53 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 21 Mae 2026 da 21:52 UTCinvestigating

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

2. 21 Mae 2026 da 22:47 UTCresolved

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

1. 19 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 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 Mae 2026 da 14:19 UTCresolved

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

1. 25 Meurzh 2026 da 09:15 UTCinvestigating

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

2. 25 Meurzh 2026 da 10:04 UTCresolved

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

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

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

1. 5 Meurzh 2026 da 09:48 UTCinvestigating

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

2. 5 Meurzh 2026 da 10:19 UTCresolved

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

3. 10 Meurzh 2026 da 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 Meurzh 2026 da 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 Cʼhwevrer 2026 da 15:53 UTCinvestigating

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

2. 4 Cʼhwevrer 2026 da 08:09 UTCresolved

   This incident has been resolved.

1. 3 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 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 Cʼhwevrer 2026 da 18:17 UTCresolved

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

3. 5 Cʼhwevrer 2026 da 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 Genver 2026 da 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 Genver 2026 da 09:47 UTCresolved

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

1. 8 Kerzu 2025 da 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 Du 2025 da 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 Du 2025 da 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