Tink 中断历史

1. 2026年7月16日 UTC 08:17investigating

   我们目前正在调查一个正在影响一些叮当产品的问题。 受影响产品的完整清单见详情.

2. 2026年7月16日 UTC 08:42identified

   这个问题已经确定,我们目前正在设法找到解决办法.

3. 2026年7月16日 UTC 08:55identified

   我们正在继续努力解决这个问题。

4. 2026年7月16日 UTC 09:11monitoring

   服务部门目前正在恢复,我们正在积极监测局势.

5. 2026年7月20日 UTC 12:47resolved

   这个问题已经得到解决。 我们为不方便而道歉.

6. 2026年7月22日 UTC 13:26postmortem

   □ 导言 7月16日9点54分到10点56分 Tink经历了一个技术问题,影响到Tink Console、Tink Link、付款启动服务、账户信息服务以及所有欧洲市场的选定风险产品。 事发期间,最终用户在开始或完成认证,同意,账户信息,付款启动等行程等方面遇到了问题,无法登录到Tink Console管理与Tink平台的整合. □ 根源分析 经过彻底调查,发现Tink的云提供商提供的外部基础设施依赖性用于通向客户的交通故障,导致基于Tink Link的用户行程中断,一些客户暂时无法使用Tink Console。 □ 补救 一旦确定问题,Tink通过另一种配置对交通造成影响,使受影响的服务恢复正常运作。 □ 后续行动 为防止今后出现类似问题,Tink将采取以下行动: 1. 加强对关键外部基础设施依赖性的监测和警报。 2. 记录和验证针对类似故障的回路回收程序。 3. 开展更多培训,以更快地查明和处理与基础设施有关的可比问题.

自动翻译自官方事件更新。

1. 2026年7月7日 UTC 13:39investigating

   我们目前正在调查一个正在影响一些叮当产品的问题。 受影响产品的完整清单见详情.

2. 2026年7月7日 UTC 13:54monitoring

   服务部门目前正在恢复,我们正在积极监测局势.

3. 2026年7月8日 UTC 13:37resolved

   这个问题已经得到解决。 我们为不方便而道歉.

4. 2026年7月9日 UTC 14:31postmortem

   ** 导言** 2026-07-07 15:26至15:51 CEST,Tink经历了一个技术问题,影响了部分客户API的可用性. 在该事件中,最终用户在获得受影响的Tink服务方面遇到了问题。 ** Root 原因分析** 经过彻底调查,查明并成功解决了引发API临时可用性问题的事件。 ** 补救** 一旦确定问题,Tink恢复了服务的提供,并实施了额外的保护措施,以提高抵御类似事件的复原力。 ** 后续行动** 为防止今后出现类似问题,Tink将采取以下行动: 1. 加强相关生产环境的保护控制。 2. 改进对影响较大的可用事件的监测和反应程序。 3. 审查和加强服务复原力,以降低类似事件的影响.

自动翻译自官方事件更新。

1. 2026年6月22日 UTC 15:13resolved

   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. 2026年6月16日 UTC 10:15identified

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

2. 2026年6月16日 UTC 11:32resolved

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

1. 2026年6月2日 UTC 09:45investigating

   We are currently investigating an issue with Payment Initiation.

2. 2026年6月2日 UTC 10:25monitoring

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

3. 2026年6月3日 UTC 08:31resolved

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

1. 2026年6月1日 UTC 00:35identified

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

2. 2026年6月1日 UTC 04:53resolved

   This incident has been resolved.

1. 2026年5月28日 UTC 16:47identified

   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. 2026年5月28日 UTC 18:02resolved

   This incident has been resolved.

1. 2026年5月21日 UTC 21:52investigating

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

2. 2026年5月21日 UTC 22:47resolved

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

1. 2026年5月19日 UTC 09:53investigating

   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. 2026年5月21日 UTC 13:29monitoring

   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. 2026年5月22日 UTC 07:39resolved

   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. 2026年5月11日 UTC 13:32investigating

   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. 2026年5月11日 UTC 14:19resolved

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

1. 2026年3月25日 UTC 09:15investigating

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

2. 2026年3月25日 UTC 10:04resolved

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

1. 2026年3月19日 UTC 21:16investigating

   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. 2026年3月20日 UTC 08:12resolved

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

1. 2026年3月5日 UTC 09:48investigating

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

2. 2026年3月5日 UTC 10:19resolved

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

3. 2026年3月10日 UTC 11:34postmortem

   **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. 2026年3月3日 UTC 13:03resolved

   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. 2026年2月3日 UTC 15:53investigating

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

2. 2026年2月4日 UTC 08:09resolved

   This incident has been resolved.

1. 2026年2月3日 UTC 10:42resolved

   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. 2026年2月2日 UTC 17:15investigating

   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. 2026年2月2日 UTC 18:17resolved

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

3. 2026年2月5日 UTC 14:21postmortem

   # 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. 2026年1月21日 UTC 09:33investigating

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

2. 2026年1月21日 UTC 09:47resolved

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

1. 2025年12月8日 UTC 10:14resolved

   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. 2025年11月24日 UTC 14:29resolved

   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. 2025年11月26日 UTC 15:50postmortem

   # 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