Istoricul incidentelor Apify

1. 20 august 2026 la 14:05 UTCinvestigating

   În prezent experimentăm performanţa platformei degradate. Actorii pot fi mai lent pentru a începe sau time out. Dacă actorii tăi sunt în pauză, îi poţi învia. Investigăm cauza acestei degradări şi vom posta actualizarea cât mai curând posibil.

2. 20 august 2026 la 14:49 UTCidentified

   Am identificat problema și lucrăm la recuperare. Performanţa Actorului este încă degradată până rezolvăm problema de bază.

3. 20 august 2026 la 15:20 UTCmonitoring

   Am rezolvat problema de bază și performanța actorului și-a revenit, acum monitorizăm situația. Dacă actorul tău fuge, îi poţi învia.

4. 20 august 2026 la 16:14 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 13 august 2026 la 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 august 2026 la 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 august 2026 la 14:05 UTCresolved

   This incident has been resolved.

1. 7 august 2026 la 21:00 UTCinvestigating

   Procurorul Google SERP se confruntă cu perioade de răspuns crescute și rate de eroare ridicate. Investigăm problema.

2. 8 august 2026 la 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 august 2026 la 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 august 2026 la 13:36 UTCidentified

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

5. 8 august 2026 la 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 august 2026 la 18:59 UTCresolved

   This incident has been resolved.

Traducere automată din actualizarea oficială a incidentului.

1. 3 august 2026 la 23:56 UTCinvestigating

   Ne confruntăm cu o gestionare lentă a cererilor pentru proxy Google SERP. Investigăm problema.

2. 4 august 2026 la 00:43 UTCinvestigating

   Google SERP Proxy nu procesează aproape nicio cerere sau este foarte lentă. Investigăm problema.

3. 4 august 2026 la 11:05 UTCidentified

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

4. 5 august 2026 la 13:30 UTCresolved

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

Traducere automată din actualizarea oficială a incidentului.

1. 26 iulie 2026 la 06:53 UTCinvestigating

   Modul actor Standby are un indice de eroare mai mare și poate necesita mai multe retries decât de obicei. Investigăm cauza. https://docs.apify.com/actors/running/standby

2. 26 iulie 2026 la 07:57 UTCresolved

   Problema a fost rezolvată. Impactul a fost o rată de eroare crescută la Actor Standby API, nu o altă componentă a fost afectată. Nu a fost nici o perioadă de timp în timpul incidentului.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 14:49 UTCidentified

   În prezent investigăm operaţiunile de sincronizare a API cauzate de operaţiunile lente ale bazei de date din cauza schimbărilor de grup.

2. 21 iulie 2026 la 16:43 UTCidentified

   Operaţiunile lente de baze de date continuă să ne afecteze sistemele. Performanţele API s-au îmbunătăţit, dar actorul se execută în prezent la timp datorită capacităţii reduse a lucrătorilor.

3. 21 iulie 2026 la 17:11 UTCmonitoring

   Acum monitorizăm situaţia. Capacitatea de lucru îmbunătățită și este acum capabil să se ocupe de rulare Actor de pornire.

4. 21 iulie 2026 la 17:47 UTCinvestigating

   Performanţele noastre de bază de date s-au degradat şi mai mult, iar întreaga platformă se confruntă cu o pană majoră. Vă vom informa pe măsură ce situaţia progresează.

5. 21 iulie 2026 la 20:33 UTCidentified

   Am identificat problema și lucrăm la redresare. Sistemul este operaţional, dar capacitatea este limitată, ceea ce duce la amortizarea funcţiilor Actor în starea "pregătită" şi la o mare parte din acestea la sincronizare.

6. 21 iulie 2026 la 20:34 UTCidentified

   Continuăm să lucrăm la o soluție pentru această problemă.

7. 21 iulie 2026 la 20:52 UTCidentified

   Actorii sunt acum pe deplin operaţionali, iar sistemul procesează toate funcţiile la timp.

8. 21 iulie 2026 la 21:28 UTCmonitoring

   Toate sistemele sunt operaţionale. Ne aşteptăm ca baza de date să-şi revină complet în 4 ore (1 am UTC). Monitorizăm performanţele platformei. Ne cerem scuze pentru orice neplăceri pe care le-ar fi putut cauza.

9. 22 iulie 2026 la 02:38 UTCresolved

   Baza de date este complet recuperată și toate sistemele sunt operaționale. Ne cerem scuze pentru orice neplăceri pe care le-ar fi putut cauza. În prezent punem în aplicare noi măsuri pentru a ne asigura că acest lucru nu se va mai întâmpla.

Traducere automată din actualizarea oficială a incidentului.

1. 21 iulie 2026 la 06:52 UTCinvestigating

   Un număr mai mare decât obişnuit de rulări Actor sunt migrate între servere, ceea ce poate provoca scurte întreruperi sau reporniri pentru unele rulări. În prezent investigăm problema.

2. 21 iulie 2026 la 06:57 UTCidentified

   Cauza migraţiilor crescute ale Actorilor a fost identificată. Rezolvăm cauza.

3. 21 iulie 2026 la 07:21 UTCmonitoring

   S-a aplicat un fix şi migraţiile actorilor revin la normal. Ne cerem scuze pentru orice neplăceri pe care le-ar fi putut cauza. Luăm această problemă în serios și vom lua măsuri pentru a evita apariția unor astfel de probleme în viitor.

4. 21 iulie 2026 la 11:53 UTCresolved

   Toate sistemele sunt operaționale, și ne cerem scuze pentru orice inconvenient acest lucru ar putea fi cauzat.

Traducere automată din actualizarea oficială a incidentului.

1. 17 iulie 2026 la 14:04 UTCinvestigating

   Vedem performanţa degradată a cererilor Google SERP. Răspunsurile pot dura mai mult decât de obicei. Investigăm problema.

2. 17 iulie 2026 la 20:08 UTCresolved

   Problema a fost rezolvată. Atât timpul de răspuns cât și rata de succes au revenit la nivelurile normale.

Traducere automată din actualizarea oficială a incidentului.

1. 4 iunie 2026 la 15:07 UTCinvestigating

   We're investigating the issue.

2. 4 iunie 2026 la 15:29 UTCidentified

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

3. 4 iunie 2026 la 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 iunie 2026 la 17:07 UTCresolved

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

1. 15 mai 2026 la 11:48 UTCinvestigating

   We're investigating the issue.

2. 15 mai 2026 la 11:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 mai 2026 la 12:19 UTCmonitoring

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

4. 16 mai 2026 la 05:28 UTCresolved

   This incident has been resolved.

1. 14 mai 2026 la 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 mai 2026 la 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 mai 2026 la 08:27 UTCresolved

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

1. 5 mai 2026 la 13:50 UTCinvestigating

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

2. 5 mai 2026 la 14:19 UTCmonitoring

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

3. 5 mai 2026 la 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 mai 2026 la 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 mai 2026 la 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 mai 2026 la 11:57 UTCresolved

   This incident has been resolved.

1. 29 aprilie 2026 la 12:35 UTCinvestigating

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

2. 29 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 15:13 UTCresolved

   This incident has been resolved.

1. 8 aprilie 2026 la 10:01 UTCinvestigating

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

2. 8 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 aprilie 2026 la 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 martie 2026 la 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 martie 2026 la 09:34 UTCresolved

   This incident has been resolved.

1. 6 martie 2026 la 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 martie 2026 la 19:05 UTCresolved

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

1. 27 ianuarie 2026 la 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 ianuarie 2026 la 05:45 UTCmonitoring

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

3. 27 ianuarie 2026 la 09:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27 ianuarie 2026 la 09:37 UTCresolved

   This incident has been resolved.

1. 21 ianuarie 2026 la 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 ianuarie 2026 la 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.