Apify kesinti geçmişi

1. 20 Ağustos 2026 14:05 UTCinvestigating

   Şu anda bozulan platform performansını yaşıyoruz. Aktörler başlamak veya zaman dışarı çıkmak için daha yavaş olabilir. Eğer Aktörleriniz zamanında giderse, onları yeniden sigortalayabilirsiniz. Bu bozulma sebebini araştırıyoruz ve güncellemeyi mümkün olduğunca kısa sürede yayınlayacağız.

2. 20 Ağustos 2026 14:49 UTCidentified

   Sorunu tespit ettik ve kurtarma üzerinde çalışıyoruz. Aktör performansı hala alt konuyu çözinceye kadar bozuluyor.

3. 20 Ağustos 2026 15:20 UTCmonitoring

   Alt konuyu çözdük ve Aktör performansı iyileşti, şimdi durumu izliyoruz. Aktörünüz zamanında çalışırsa, onları yeniden sigortalayabilirsiniz.

4. 20 Ağustos 2026 16:14 UTCresolved

   Bu olay çözüldü.

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

1. 13 Ağustos 2026 15:38 UTCidentified

   We are seeing elevated error rates on the SHADER proxy group connected with issues with one of our upstream providers. If you use this proxy group directly (not through the virtual AUTO proxy group), please switch to using another group (such as BUYPROXIES94952) temporarily.

2. 13 Ağustos 2026 20:08 UTCmonitoring

   A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.

3. 14 Ağustos 2026 14:05 UTCresolved

   This incident has been resolved.

1. 7 Ağustos 2026 21:00 UTCinvestigating

   Google SERP proxy zaman ve yüksek hata oranları arttı. Sorunu araştırıyoruz.

2. 8 Ağustos 2026 10:18 UTCidentified

   The performance problems are caused by issues with our upstream providers. We are in contact with them to find a solution.

3. 8 Ağustos 2026 10:19 UTCidentified

   We have applied partial fixes to improve the situation and lower the error rate. We are still seeing an elevated error rate and are continuing to work on reaching a full resolution.

4. 8 Ağustos 2026 13:36 UTCidentified

   The success rate and latency is continuing to improve to almost normal levels, we expect full recovery soon.

5. 8 Ağustos 2026 18:58 UTCmonitoring

   We have seen a full recovery of the SERP proxy success rates. We will continue monitoring for any future degradation.

6. 8 Ağustos 2026 18:59 UTCresolved

   This incident has been resolved.

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

1. 3 Ağustos 2026 23:56 UTCinvestigating

   Google SERP proxy için yavaş istekler yaşıyoruz. Sorunu araştırıyoruz.

2. 4 Ağustos 2026 00:43 UTCinvestigating

   Google SERP Proxy neredeyse herhangi bir istek işlemez veya çok yavaştır. Sorunu araştırıyoruz.

3. 4 Ağustos 2026 11:05 UTCidentified

   The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.

4. 5 Ağustos 2026 13:30 UTCresolved

   The Google SERP Proxy is stabilized, and we continue to monitor its performance.

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

1. 26 Temmuz 2026 06:53 UTCinvestigating

   Aktör Standby modu daha yüksek bir hata oranına sahiptir ve normalden daha fazla retries gerektirebilir. Nedeni araştırıyoruz. https://docs.apify.com/actors / running/standby

2. 26 Temmuz 2026 07:57 UTCresolved

   Sorun çözüldü. Etkisi, Aktör Standby API'de artan bir hata oranıydı, başka bir bileşen etkilenmedi. Olay döneminde aşağı zaman yoktu.

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

1. 21 Temmuz 2026 14:49 UTCidentified

   Şu anda küme değişiklikleri nedeniyle yavaş veritabanı operasyonlarının neden olduğu API üzerinde zamanlamayı araştırıyoruz.

2. 21 Temmuz 2026 16:43 UTCidentified

   Yavaş veritabanı işlemleri sistemlerimizi etkilemeye devam ediyor. API performansı gelişmiştir, ancak Aktör şu anda işçi kapasitesinin azaltılması nedeniyle zamanlanıyor.

3. 21 Temmuz 2026 17:11 UTCmonitoring

   Şimdi durumu takip ediyoruz. Worker kapasite gelişmiştir ve şimdi başlangıç Aktörünün çalışmasını idare edebilir.

4. 21 Temmuz 2026 17:47 UTCinvestigating

   Veritabanı küme performansımız daha da bozuldu ve tüm platform büyük bir kesintiyle karşı karşıya. Sizi durum ilerledikçe bilgilendireceğiz.

5. 21 Temmuz 2026 20:33 UTCidentified

   Sorunu tespit ettik ve iyileşmeye doğru çalışıyoruz. Sistem operasyoneldir, ancak kapasite kapılır, çünkü Aktör “okuyucu” durumda ve onların büyük bir kısmını zamanlamasıyla karşılaşır.

6. 21 Temmuz 2026 20:34 UTCidentified

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

7. 21 Temmuz 2026 20:52 UTCidentified

   Aktörler şimdi tamamen çalışır ve sistem her zaman çalışır.

8. 21 Temmuz 2026 21:28 UTCmonitoring

   Tüm sistemler operasyoneldir. Veritabanının 4 saat içinde tamamen iyileşmesini bekliyoruz (1 UTC). Platformun performansını izliyoruz. Bunun sebep olabileceği herhangi bir rahatsızlıktan özür dileriz.

9. 22 Temmuz 2026 02:38 UTCresolved

   Veritabanı tamamen restore edilir ve tüm sistemler çalışır. Bunun sebep olabileceği herhangi bir rahatsızlıktan özür dileriz. Şu anda bunun tekrar gerçekleşmeyeceğini sağlamak için yeni önlemler uyguluyoruz.

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

1. 21 Temmuz 2026 06:52 UTCinvestigating

   Daha yüksek çözünürlüklü bir Aktörün sayısı, bazı işler için kısa kesintilere veya yeniden başlatmalara neden olabilecek sunucular arasında göç edilmektedir. Şu anda konuyu araştırıyoruz.

2. 21 Temmuz 2026 06:57 UTCidentified

   Yüksek Aktör koşu göçlerinin nedeni tespit edilmiştir. Nedeni çözdük.

3. 21 Temmuz 2026 07:21 UTCmonitoring

   Bir düzeltme uygulandı ve Aktör koşu göçleri normale dönüyor. Bunun sebep olabileceği herhangi bir rahatsızlıktan özür dileriz. Bu sorunu ciddiye alıyoruz ve gelecekte meydana gelen bu tür sorunlardan kaçınmak için adımlar atacağız.

4. 21 Temmuz 2026 11:53 UTCresolved

   Tüm sistemler çalışır ve bunun sebep olabileceği herhangi bir rahatsızlıktan özür dileriz.

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

1. 17 Temmuz 2026 14:04 UTCinvestigating

   Google SERP isteklerinin degraded performansını görüyoruz. Yanıtlar her zamankinden daha uzun sürebilir. Sorunu araştırıyoruz.

2. 17 Temmuz 2026 20:08 UTCresolved

   Sorun çözüldü. Hem tepki süresi hem de başarı oranı normal seviyelere geri döndü.

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

1. 4 Haziran 2026 15:07 UTCinvestigating

   We're investigating the issue.

2. 4 Haziran 2026 15:29 UTCidentified

   The issue has been identified, and we are resolving it.

3. 4 Haziran 2026 15:34 UTCmonitoring

   We have identified and resolved the root cause of the issue. No data loss occurred, as all webhooks are automatically retried. A backlog of pending webhooks remains and is currently being processed. We are monitoring the situation closely.

4. 4 Haziran 2026 17:07 UTCresolved

   Webhooks are operational, and we apologize for any inconvenience this might have caused.

1. 15 Mayıs 2026 11:48 UTCinvestigating

   We're investigating the issue.

2. 15 Mayıs 2026 11:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 Mayıs 2026 12:19 UTCmonitoring

   We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.

4. 16 Mayıs 2026 05:28 UTCresolved

   This incident has been resolved.

1. 14 Mayıs 2026 08:21 UTCresolved

   We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally. We apologize for the inconvenience.

1. 6 Mayıs 2026 20:08 UTCidentified

   OAuth sign-in to mcp.apify.com from clients using CIMD with loopback redirects (currently Claude Code) is failing due to a regression. Existing connections and other clients (claude.ai, Cursor, Codex) are unaffected (the later use DCR). We are sorry for the inconvenience and working on a fix.

2. 7 Mayıs 2026 08:27 UTCresolved

   We have implemented a fix for the OAuth flow, and the connections are now working normally.

1. 5 Mayıs 2026 13:50 UTCinvestigating

   We're experiencing outage of key-value store. We're investigation the cause of the issue

2. 5 Mayıs 2026 14:19 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 5 Mayıs 2026 14:34 UTCresolved

   We've resolved an issue where a key-value store API update caused some Actor runs to time out. If your Actor run timed out you can get it back by resurrecting it. There was no data loss. We sincerely apologize for any inconvenience this may have caused.

1. 1 Mayıs 2026 11:23 UTCidentified

   We have identified an issue causing degraded performance in the Console UI and in some API requests. We have implemented a fix, and the performance should stabilize soon.

2. 1 Mayıs 2026 11:29 UTCmonitoring

   Console UI and API performance should be back to standard levels. We will monitor the situation while we investigate the incident's root cause.

3. 1 Mayıs 2026 11:57 UTCresolved

   This incident has been resolved.

1. 29 Nisan 2026 12:35 UTCinvestigating

   We're experiencing degraded performance. We're investigation the cause of the issue

2. 29 Nisan 2026 13:07 UTCinvestigating

   We're experiencing a full outage of Actors and API. Actors might not be starting. Our engineering team is investigating the root cause of the issue.

3. 29 Nisan 2026 13:35 UTCinvestigating

   We've identified the root cause of the issue, and our engineering team is monitoring the metrics. Console, Actors, and API should be stable now.

4. 29 Nisan 2026 15:13 UTCresolved

   This incident has been resolved.

1. 8 Nisan 2026 10:01 UTCinvestigating

   We are investigating slow API response times due to underlying database issues.

2. 8 Nisan 2026 18:25 UTCidentified

   We’ve identified the root cause and have resolved a part of the issue, but the system has not yet fully stabilized. The Actor Runs list endpoint (https://api.apify.com/v2/acts/:actorId/runs) remains the most impacted, along with related views in the Apify Console, where we are still actively working on a fix. Additional endpoints may also experience degraded performance. At this time, we cannot provide an estimate for full resolution.

3. 8 Nisan 2026 20:35 UTCinvestigating

   Our systems are currently experiencing a major disruption. We sincerely apologize and are actively investigating the root cause. We will provide updates as more information becomes available.

4. 8 Nisan 2026 21:16 UTCidentified

   Service has partially recovered, and we are currently experiencing degraded performance. We are actively investigating the issue and working on a fix. We will continue to provide updates as more information becomes available.

5. 8 Nisan 2026 22:24 UTCmonitoring

   The Apify platform is fully recovered. The incident followed a database cluster sharding procedure that resulted in a performance impact on some operations. There was no data loss. The Actor run list API endpoint experienced performance issues between 10:00 and 20:30 UTC, followed by a partial outage of all services from 20:30 to 21:10. Now everything is back to normal, and we are monitoring the situation. We are sorry for any inconvenience caused.

6. 9 Nisan 2026 09:15 UTCresolved

   All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.

1. 11 Mart 2026 12:48 UTCmonitoring

   We are informing you about a security incident that occurred on March 6, 2026. Based on our investigation to date, there is no indication that any customer data was affected or compromised. However, we want to share the information we have with you as part of our ongoing commitment to transparency. What happened At approximately 21:52 UTC on March 6, 2026, we detected that the GitHub account of one of our employees had been compromised as part of a broader, known malware campaign. The attacker used this access to inject malicious code into multiple branches across our GitHub repositories via force-pushed commits. Thanks to branch protection rules in place on our repositories, no changes were merged into any default or protected branches. How we responded Upon detection, we immediately suspended the affected account and blocked all associated access across our internal systems. Our engineering team then identified all affected branches and reverted every malicious commit. Full cleanup was completed by approximately 00:32 UTC on March 7, 2026. What we have investigated We have since conducted a thorough review of our GitHub audit logs, AWS CloudTrail logs, Google Workspace logs, and all other important resources. All activity reviewed was consistent with expected patterns — no unauthorized access, no suspicious logins, and no signs of data exfiltration were identified beyond the GitHub repository commits, which have been fully reverted. Despite no signs of malicious access, we also completed the rotation of secrets and the scan of all working machines used by Apify employees. Impact on your data Based on our investigation to date, there is no evidence that any customer data was accessed or affected by this incident. The attack was limited to source code repository branches, all of which were protected and have been restored. We take the security of your data seriously and will continue analyzing the impact of the issue and monitoring for any further indicators of compromise. We will provide an update if our ongoing investigation reveals any new findings. Please don't hesitate to reach out to [email protected] if you have any questions. Sincerely, The Apify security team

2. 12 Mart 2026 09:34 UTCresolved

   This incident has been resolved.

1. 6 Mart 2026 17:27 UTCidentified

   We are currently experiencing degraded performance of the datacenter proxy. The root cause has been identified and we are working on a fix.

2. 6 Mart 2026 19:05 UTCresolved

   Datacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused.

1. 27 Ocak 2026 04:10 UTCinvestigating

   We are currently investigating an issue affecting residential proxies. Some requests are failing or timing out. Our team is actively working to identify the root cause and restore normal operation. Further updates will be provided as we learn more.

2. 27 Ocak 2026 05:45 UTCmonitoring

   The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.

3. 27 Ocak 2026 09:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27 Ocak 2026 09:37 UTCresolved

   This incident has been resolved.

1. 21 Ocak 2026 15:17 UTCidentified

   Apify Console is temporarily unavailable. We have identified the issue and are rolling out the fix. There is no data loss associated with this outage and Actor runs should not be affected.

2. 21 Ocak 2026 15:19 UTCresolved

   All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen again.