Tink 장애 기록

1. 2026년 7월 16일 AM 8:17 UTCinvestigating

   우리는 현재 여러 Tink 제품에 영향을 미치는 문제점을 조사하고 있습니다. 영향을받는 제품의 전체 목록에 대한 세부 정보를 참조하십시오.

2. 2026년 7월 16일 AM 8:42 UTCidentified

   문제는 확인되었으며 현재 솔루션에서 일하고 있습니다.

3. 2026년 7월 16일 AM 8:55 UTCidentified

   이 문제를 해결하기 위해 계속 노력하고 있습니다.

4. 2026년 7월 16일 AM 9:11 UTCmonitoring

   서비스는 현재 회복되고 우리는 상황을 적극적으로 모니터링하고 있습니다.

5. 2026년 7월 20일 PM 12:47 UTCresolved

   이 문제는 해결되었습니다. 우리는 불편을 끼쳐 드려요.

6. 2026년 7월 22일 PM 1:26 UTCpostmortem

   ## 소개 에 16 7월 사이 09:54 과 10:56 CEST Tink는 Tink Console, Tink Link, Payment Initiation Services, Account Information Services 및 모든 유럽 시장에 대한 위험 제품에 영향을 미치는 기술 문제를 경험했습니다. 사건의 시간 동안, 최종 사용자는 시작 또는 인증 완료, 동의, 계정 정보, 결제 개시 여행 및 Tink 콘솔에 로그인 할 수 없으며 Tink 플랫폼과 통합을 관리 할 수 없습니다. ## 뿌리 원인 분석 철저한 조사 후, Tink의 클라우드 공급자가 Tink Link 기반 사용자 여행 및 일부 고객에 대한 Tink 콘솔 액세스의 일시적 장애를 중단하는 데 사용되는 외부 인프라 의존성이 있음을 발견했습니다. ## 구제 문제가 확인되면, Tink는 대체 구성을 통해 영향을받은 트래픽을 경로를 통과하고 정상 작동에 영향을받는 서비스를 복원했습니다. ## 팔로우 작업 미래의 비슷한 문제를 방지하기 위해, Tink는 다음과 같은 작업을 수행 할 것이다 : 1. 중요한 외부 인프라 의존성에 대한 모니터링 및 경고 향상. 2. 유사한 실패의 주위에 여정을 위한 문서와 유효한 회복 절차. 3. 빠른 ID 및 Comparable 인프라 관련 문제의 취급을 위한 추가 훈련을 실행하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 7일 PM 1:39 UTCinvestigating

   우리는 현재 여러 Tink 제품에 영향을 미치는 문제점을 조사하고 있습니다. 영향을받는 제품의 전체 목록에 대한 세부 정보를 참조하십시오.

2. 2026년 7월 7일 PM 1:54 UTCmonitoring

   서비스는 현재 회복되고 우리는 상황을 적극적으로 모니터링하고 있습니다.

3. 2026년 7월 8일 PM 1:37 UTCresolved

   이 문제는 해결되었습니다. 우리는 불편을 끼쳐 드려요.

4. 2026년 7월 9일 PM 2:31 UTCpostmortem

   ** 소개** 15:26 및 15:51 CEST 사이 2026-07-07에, Tink는 우리의 고객의 일부에 대한 API 가용성에 영향을 미치는 기술 문제를 경험했습니다. 사건 중, 최종 사용자는 영향을받는 Tink 서비스에 액세스하는 데 문제가 있습니다. ** 루트 원인 분석 ** 철저한 조사 후에, 임시 API 가용성 문제점을 방아쇠를 당기는 사건은 확인되고 성공적으로 해결되었습니다. **치료** 문제가 확인되면, Tink는 서비스 가용성을 복원하고 유사한 사건에 대한 탄력을 개선하기 위해 추가 보호 조치를 구현했습니다. **Follow-up 액션 ** 미래의 비슷한 문제를 방지하기 위해, Tink는 다음과 같은 작업을 수행 할 것이다 : 1. 관련 생산 환경의 맞은편에 방어적인 통제를 강화하십시오. 2. 높은 충격 가용성 사건을 위한 감시 그리고 응답 절차를 개량하십시오. 3. 유사한 사건의 충격을 감소시키는 서비스 탄력을 검토하고 강화하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 22일 PM 3: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. 2026년 6월 16일 AM 10:15 UTCidentified

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

2. 2026년 6월 16일 AM 11:32 UTCresolved

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

1. 2026년 6월 2일 AM 9:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2026년 6월 2일 AM 10:25 UTCmonitoring

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

3. 2026년 6월 3일 AM 8:31 UTCresolved

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

1. 2026년 6월 1일 AM 12:35 UTCidentified

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

2. 2026년 6월 1일 AM 4:53 UTCresolved

   This incident has been resolved.

1. 2026년 5월 28일 PM 4: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. 2026년 5월 28일 PM 6:02 UTCresolved

   This incident has been resolved.

1. 2026년 5월 21일 PM 9:52 UTCinvestigating

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

2. 2026년 5월 21일 PM 10:47 UTCresolved

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

1. 2026년 5월 19일 AM 9: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. 2026년 5월 21일 PM 1: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. 2026년 5월 22일 AM 7: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. 2026년 5월 11일 PM 1: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. 2026년 5월 11일 PM 2:19 UTCresolved

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

1. 2026년 3월 25일 AM 9:15 UTCinvestigating

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

2. 2026년 3월 25일 AM 10:04 UTCresolved

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

1. 2026년 3월 19일 PM 9: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. 2026년 3월 20일 AM 8:12 UTCresolved

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

1. 2026년 3월 5일 AM 9:48 UTCinvestigating

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

2. 2026년 3월 5일 AM 10:19 UTCresolved

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

3. 2026년 3월 10일 AM 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. 2026년 3월 3일 PM 1: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. 2026년 2월 3일 PM 3:53 UTCinvestigating

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

2. 2026년 2월 4일 AM 8:09 UTCresolved

   This incident has been resolved.

1. 2026년 2월 3일 AM 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. 2026년 2월 2일 PM 5: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. 2026년 2월 2일 PM 6:17 UTCresolved

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

3. 2026년 2월 5일 PM 2: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. 2026년 1월 21일 AM 9:33 UTCinvestigating

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

2. 2026년 1월 21일 AM 9:47 UTCresolved

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

1. 2025년 12월 8일 AM 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. 2025년 11월 24일 PM 2: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. 2025년 11월 26일 PM 3: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