Knock App kesinti geçmişi

1. 1 Ekim 2026 14:09 UTCidentified

   Müşteri veri depolarına senkronizasyon gecikiyor. gecikmeyi çözmeye çalışıyoruz. Diğer veri senkronizasyonu etkilenmez.

2. 1 Ekim 2026 16:06 UTCidentified

   Veri deposuna aktif olarak mevcut mesajı tekrar sunuyoruz ve önümüzdeki 3 saatte tamamlamak için bunu bekliyoruz. O zaman, tarih verilerine kadar tüm alt konumlara yeni bir senkronize edeceğiz.

3. 2 Ekim 2026 02:56 UTCidentified

   İhracat için en güncel mesajı verileri almaya aktif olarak çalışıyoruz. İş, koşmak için genişletilmiş bir zaman alıyor. Bu iş tamamlandıktan sonra senkronize senkronizasyonlar yapacağız.

4. 2 Ekim 2026 04:16 UTCmonitoring

   İhracat için masaları başarıyla yeniden inşa ettik ve şimdi senkronize ediyoruz. İzlemeye devam ediyoruz ve önümüzdeki günlerde bazı iyileştirmeler ve daha da stabilizasyon üzerinde çalışacağız.

5. 2 Ekim 2026 21:05 UTCresolved

   Veri depo bağlantımız için normal senkronizasyon programlarına geri döndük.

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

1. 21 Eylül 2026 18:22 UTCinvestigating

   Şu anda bir konu üzerinde paniğe giriş yaptık. Google ile oturum açma ve geçkey etkilenmez. API aracılığıyla gönderilen mesaj etkilenmez.

2. 21 Eylül 2026 18:41 UTCmonitoring

   Bir düzeltme uygulandı ve şu anda hizmeti izliyoruz.

3. 21 Eylül 2026 19:24 UTCresolved

   Bu olay çözüldü ve sihirli bağlantı girişi tamamen işlevsel. Mali aktivite, e-posta sağlayıcımıza, Knock panosunun işlem e-postalarını bayrağına neden oldu, sihirli bağlantı teslim edilebilirliği bozdu. Faaliyeti engelledik ve e-posta teslimatını geri aldık. Sadece Knock'in e-postaları [email protected] etkilendi. Müşteri e-posta kanalları etkilenmedi.

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

1. 31 Ağustos 2026 16:42 UTCidentified

   Bazı müşteriler iş akış işlemesinde hataları görebilir. Sorunu tespit ettik ve bir düzeltme yapıyoruz.

2. 31 Ağustos 2026 16:59 UTCmonitoring

   Bir düzeltme uygulandı ve şu anda hizmeti izliyoruz. Daha önceki başarısız iş akışları yeniden beslenmektedir.

3. 31 Ağustos 2026 17:35 UTCmonitoring

   Bir düzeltme uygulandı ve şu anda hizmeti izliyoruz.

4. 31 Ağustos 2026 18:26 UTCresolved

   Bu olay şimdi çözüldü ve hizmet şimdi tamamen operasyonel.

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

1. 30 Temmuz 2026 18:10 UTCinvestigating

   Şu anda veri depolama ihracatlarımızla bir gecikme araştırıyoruz. Yakında bir güncelleme yayınlayacağız.

2. 31 Temmuz 2026 16:49 UTCresolved

   Bu olay şimdi çözüldü ve hizmet şimdi tamamen operasyonel.

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

1. 17 Temmuz 2026 19:37 UTCinvestigating

   Dashboard ve V1 API'de iş akışlarının gecikmelerini araştırıyoruz. Şu anda bazı koşu logları için 18 dakikaya kadar gecikmeleri görüyoruz.

2. 17 Temmuz 2026 19:57 UTCresolved

   Bu olay şimdi çözüldü ve hizmet şimdi tamamen operasyonel.

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

1. 16 Temmuz 2026 15:32 UTCinvestigating

   Şu anda bildirim iş akışlarını işlemek ve bazı müşteriler için mesajlar gönderiyoruz.

2. 16 Temmuz 2026 15:35 UTCidentified

   Bir düzeltme gönderdik ve kurtarma görmeye başlıyoruz. yakından izlemeye devam ediyoruz.

3. 16 Temmuz 2026 15:40 UTCmonitoring

   İş akışı işleme ve mesaj teslimi tekrar çalışır. yakından izlemeye devam ediyoruz.

4. 16 Temmuz 2026 15:45 UTCresolved

   Bu olay şimdi çözüldü ve hizmet şimdi tamamen operasyonel.

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

1. 10 Temmuz 2026 15:17 UTCinvestigating

   We're currently investigating an issue with our service. We'll have an update soon.

2. 10 Temmuz 2026 15:28 UTCidentified

   We've identified the issue with the service and are actively working on a fix. We're seeing workflows and message deliveries process again at the usual rate.

3. 10 Temmuz 2026 15:33 UTCmonitoring

   A fix has been implemented, and we're currently monitoring the service. All our services seem to be recovering. We're in the process of replaying any failed work that happened during the window. We expect there was no loss of workflows during this incident, but some work may have been delayed.

4. 10 Temmuz 2026 15:40 UTCresolved

   This incident has now been resolved and the service is now fully operational. We're replaying any jobs that may have failed during the window. All our processing queues are fully caught up. We will share a full post mortem as soon as possible.

1. 1 Temmuz 2026 21:53 UTCmonitoring

   Message data synchronization into downstream customer data warehouse destinations is delayed for messages created after 8 PM ET on June 30, 2026. We have implemented a fix. We expect the issue to be fully resolved following the nightly synchronization job scheduled on July 2nd, 2026.

2. 3 Temmuz 2026 00:12 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 24 Haziran 2026 14:00 UTCinvestigating

   We are investigating delays processing workflow run event logs.

2. 24 Haziran 2026 17:26 UTCinvestigating

   We're still investigating delays affecting workflow run event logs.

3. 24 Haziran 2026 17:50 UTCresolved

   We've completely recovered any lag on workflow logs and we are back to normal.

4. 25 Haziran 2026 15:30 UTCinvestigating

   We're currently investigating an issue with some workflow logs being delayed.

5. 26 Haziran 2026 06:35 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 16 Haziran 2026 17:55 UTCinvestigating

   We're currently investigating elevated error rates connecting to the V1 Websocket API. Realtime behavior for in-app feed and guides is degraded as a result.

2. 16 Haziran 2026 18:26 UTCmonitoring

   We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely.

3. 16 Haziran 2026 18:44 UTCresolved

   This incident has been resolved.

1. 16 Haziran 2026 13:34 UTCinvestigating

   We are investigating delays in ingesting workflow run logs and triggering outbound webhooks from workflow run events.

2. 16 Haziran 2026 13:36 UTCmonitoring

   We are seeing recovery in workflow run log and webhook delivery delays and are continuing to monitor.

3. 16 Haziran 2026 13:38 UTCresolved

   This incident has been resolved.

1. 15 Haziran 2026 14:35 UTCmonitoring

   We intermittently experienced delayed workflow logs between ~09:00 AM UTC and ~01:45 PM UTC today (2026/06/15). This was caused by some internal changes in how we fan out workflow logs, which caused consumers to get temporarily backlogged. The peak delay we experienced before processing workflow logs was around 15 minutes, but we intermittently saw delays of up to 5-6 minutes. This affected 1. Logs showing up in the dashboard. 2. Workflow batch mappings. We saw complete resolution at 01:43 PM UTC. Logs are being processed within our usual window (within up to ~5s) again.

2. 15 Haziran 2026 16:31 UTCresolved

   We did not experience any further issues after we put the fix in place.

1. 4 Haziran 2026 11:40 UTCinvestigating

   We're seeing elevated response times loading some log data. This is leading to slower page loads in the Dashboard and slower responses from some V1 API endpoints.

2. 4 Haziran 2026 12:07 UTCmonitoring

   We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving.

3. 4 Haziran 2026 12:11 UTCresolved

   This incident has been resolved.

1. 1 Mayıs 2026 17:25 UTCinvestigating

   We're currently investigating an issue with our service. We'll have an update soon.

2. 1 Mayıs 2026 17:30 UTCmonitoring

   A fix has been implemented, and we're currently monitoring the service.

3. 1 Mayıs 2026 18:26 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 1 Mayıs 2026 10:19 UTCinvestigating

   We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed

2. 1 Mayıs 2026 10:33 UTCinvestigating

   We're seeing an extremely high amount of load on our services which is causing workflow and broadcast delays. We're working to relieve the pressure immediately.

3. 1 Mayıs 2026 10:56 UTCinvestigating

   We're seeing some recovery on our services but are dealing with delays in some workflow and broadcast processing still. Our logging service is also currently delayed, so may not reflect the latest as we catch up and work through a huge influx of work.

4. 1 Mayıs 2026 11:22 UTCidentified

   One of our workflow queues is currently still backlogged, but we're seeing good resolution across other areas of our service and we have effectively cordoned off the source of the issue. We're burning through remaining work and are exploring ways to shed the load further to get back to stability.

5. 1 Mayıs 2026 12:05 UTCidentified

   We've taken steps to shuffle around work in our system which has meant that we're processing new work for all customers again. We still have some queued workflow executions that we're working through and expect to be fully caught up in the next 40 minutes.

6. 1 Mayıs 2026 12:58 UTCidentified

   We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.

7. 1 Mayıs 2026 13:18 UTCresolved

   All behavior remains normal, we are considering this incident resolved.

1. 14 Nisan 2026 15:09 UTCinvestigating

   We are investigating errors resolving and redirecting tracked links.

2. 14 Nisan 2026 15:14 UTCmonitoring

   We've shipped a fix and are seeing resolution in tracked link resolution. We are monitoring closely.

3. 14 Nisan 2026 15:19 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 31 Mart 2026 13:06 UTCinvestigating

   We're currently investigating an issue with delayed ingestion of our API logs, putting pressure on our ingestion pipeline and resulting in some degraded state for browsing API logs as well.

2. 31 Mart 2026 13:29 UTCmonitoring

   We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely.

3. 31 Mart 2026 13:50 UTCmonitoring

   We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident

4. 31 Mart 2026 14:18 UTCresolved

   This incident has now been resolved and the service is now fully operational.

1. 25 Mart 2026 15:29 UTCinvestigating

   We are investigating delays in creating and processing message events. Some customers may experience delays seeing message events in the Knock Dashboard. Some customers may also experience delays in outbound webhook events triggered by message events.

2. 25 Mart 2026 16:21 UTCidentified

   We've implemented a fix and are seeing message event lag begin to recover.

3. 25 Mart 2026 16:22 UTCidentified

   Webhook delivery lag has resolved. We are still waiting for message event Dashboard availability lag to recover.

4. 25 Mart 2026 16:36 UTCresolved

   All message event lag has recovered. We are considering this incident resolved.

1. 20 Mart 2026 00:33 UTCinvestigating

   We're currently investigating an issue with promoting workflows. We're working on a fix now. This does not impact notification delivery.

2. 20 Mart 2026 00:47 UTCidentified

   We've identified the issue with workflow promotion and are deploying a fix for it now.

3. 20 Mart 2026 00:54 UTCresolved

   The fix has been deployed and workflows are able to be promoted again.

1. 3 Mart 2026 17:02 UTCinvestigating

   We're currently investigating an issue with log processing. There are no issues currently processing workflows and messages, but logs are affected.

2. 3 Mart 2026 17:23 UTCidentified

   We've identified the issue with the service and are actively working on a fix.

3. 3 Mart 2026 17:24 UTCmonitoring

   A fix has been implemented, and we're currently monitoring the service.

4. 3 Mart 2026 17:32 UTCresolved

   This incident has now been resolved and the service is now fully operational.