Tink kesinti geçmişi

1. 16 Temmuz 2026 08:17 UTCinvestigating

   Şu anda birkaç Tink ürünlerini etkileyen bir sorunu araştırıyoruz. Etkilenen ürünlerin tam listesi için ayrıntıları görün.

2. 16 Temmuz 2026 08:42 UTCidentified

   Sorun tespit edildi ve şu anda bir çözüm üzerinde çalışıyoruz.

3. 16 Temmuz 2026 08:55 UTCidentified

   Bu sorun için bir düzeltme üzerinde çalışmaya devam ediyoruz.

4. 16 Temmuz 2026 09:11 UTCmonitoring

   Servis şu anda geri dönüyor ve durumu aktif olarak izliyoruz.

5. 20 Temmuz 2026 12:47 UTCresolved

   Bu konu çözüldü. Bu rahatsızlıktan özür dileriz.

6. 22 Temmuz 2026 13:26 UTCpostmortem

   ## Introduction 16 Temmuz'da 09:54 ve 10:56 CEST Tink Console, Tink Link, Ödeme Teşvik Hizmetleri, Hesap Bilgileri Hizmetleri ve tüm Avrupa pazarları için risk ürünlerini içeren teknik bir sorun yaşadı. Olay sırasında, son kullanıcılar, kimlik doğrulama, onay, hesap-bilgileri ve ödeme-inititasyon yolculukları ile entegrasyonlarını yönetmek için konuları deneyimliyorlardı. ## Root Cause Analysis Kapsamlı bir soruşturmadan sonra, Tink'in bulut sağlayıcı tarafından sağlanan dışsal bir altyapının, müşteri odaklı trafik arızası için kullanılan bulut sağlayıcı tarafından sağlanan bir bağımlılığın, Tink Link tabanlı kullanıcı yolculuklarının ve bazı müşteriler için geçici olarak yetersiz kalmasına yol açtı. ## Remediation Sorun tespit edildikten sonra, Tink rotalı trafiği alternatif bir yapılandırma yoluyla etkiledi ve etkilenen hizmetleri normal operasyona geri getirdi. ## Takip eylemleri Gelecekte benzer sorunları önlemek için, Tink aşağıdaki eylemleri uygulayacaktır: 1. kritik dış altyapı bağımlılıkları için izleme ve uyarma. 2. Doküman ve benzer başarısızlıklar hakkında kurtarma prosedürlerini onaylayın. 3. Daha hızlı tanımlama ve karşılaştırılabilir altyapıyla ilgili sorunları işlemek için ek eğitim yapın.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 7 Temmuz 2026 13:39 UTCinvestigating

   Şu anda birkaç Tink ürünlerini etkileyen bir sorunu araştırıyoruz. Etkilenen ürünlerin tam listesi için ayrıntıları görün.

2. 7 Temmuz 2026 13:54 UTCmonitoring

   Servis şu anda geri dönüyor ve durumu aktif olarak izliyoruz.

3. 8 Temmuz 2026 13:37 UTCresolved

   Bu konu çözüldü. Bu rahatsızlıktan özür dileriz.

4. 9 Temmuz 2026 14:31 UTCpostmortem

   **Introduction** 15:26 ve 15:51 CEST arasında 2026-07-07-07'de, Tink bazı müşterilerimiz için API'yi etkileyen bir teknik sorun yaşadı. Olay sırasında, son kullanıcılar etkilenen Tink servislerine erişmekle ilgili sorunlar yaşadı. **Root Cause Analizi** Kapsamlı bir soruşturmadan sonra, geçici API erişilebilirliğini tetikleyen olay tespit edildi ve başarıyla ele alındı. **R capturedation** Sorun tespit edildiğinde, Tink restore edilmiş hizmet kullanılabilirliği ve benzer olaylara karşı dayanıklılık geliştirmek için ek koruyucu önlemler uygulandı. ** Takip Eylemleri ** Gelecekte benzer sorunları önlemek için, Tink aşağıdaki eylemleri uygulayacaktır: 1. İlgili üretim ortamlarında koruyucu kontrolleri güçlendirin. 2. Yüksek kullanılabilirlik olayları için izleme ve yanıt prosedürleri geliştirmek. 3. Benzer olayların etkisini azaltmak için servis direncini gözden geçirin.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

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

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

2. 16 Haziran 2026 11:32 UTCresolved

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

1. 2 Haziran 2026 09:45 UTCinvestigating

   We are currently investigating an issue with Payment Initiation.

2. 2 Haziran 2026 10:25 UTCmonitoring

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

3. 3 Haziran 2026 08:31 UTCresolved

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

1. 1 Haziran 2026 00:35 UTCidentified

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

2. 1 Haziran 2026 04:53 UTCresolved

   This incident has been resolved.

1. 28 Mayıs 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 Mayıs 2026 18:02 UTCresolved

   This incident has been resolved.

1. 21 Mayıs 2026 21:52 UTCinvestigating

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

2. 21 Mayıs 2026 22:47 UTCresolved

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

1. 19 Mayıs 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 Mayıs 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 Mayıs 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 Mayıs 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 Mayıs 2026 14:19 UTCresolved

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

1. 25 Mart 2026 09:15 UTCinvestigating

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

2. 25 Mart 2026 10:04 UTCresolved

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

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

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

1. 5 Mart 2026 09:48 UTCinvestigating

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

2. 5 Mart 2026 10:19 UTCresolved

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

3. 10 Mart 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 Mart 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 Şubat 2026 15:53 UTCinvestigating

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

2. 4 Şubat 2026 08:09 UTCresolved

   This incident has been resolved.

1. 3 Şubat 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 Şubat 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 Şubat 2026 18:17 UTCresolved

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

3. 5 Şubat 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 Ocak 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 Ocak 2026 09:47 UTCresolved

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

1. 8 Aralık 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 Kasım 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 Kasım 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