Historial de interrupciones de Apify

1. August 20, 2026 at 2:05 PM UTCinvestigating

   Actualmente estamos experimentando un rendimiento de plataforma degradado. Los actores pueden ser más lentos para empezar o salir del tiempo. Si tus Actores salen, puedes resucitarlos. Estamos investigando la causa de esta degradación y publicaremos la actualización lo antes posible.

2. August 20, 2026 at 2:49 PM UTCidentified

   Hemos identificado el problema y estamos trabajando en recuperación. El rendimiento de Actor sigue degradado hasta que resuelva el problema subyacente.

3. August 20, 2026 at 3:20 PM UTCmonitoring

   Hemos resuelto el problema subyacente y el rendimiento de Actor se ha recuperado, ahora estamos monitoreando la situación. Si tu Actor se agota, puedes resucitarlos.

4. August 20, 2026 at 4:14 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 13, 2026 at 3:38 PM 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. August 13, 2026 at 8:08 PM UTCmonitoring

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

3. August 14, 2026 at 2:05 PM UTCresolved

   This incident has been resolved.

1. August 7, 2026 at 9:00 PM UTCinvestigating

   El proxy de Google SERP está experimentando mayores tiempos de respuesta y tasas de error elevadas. Estamos investigando el tema.

2. August 8, 2026 at 10:18 AM UTCidentified

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

3. August 8, 2026 at 10:19 AM 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. August 8, 2026 at 1:36 PM UTCidentified

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

5. August 8, 2026 at 6:58 PM UTCmonitoring

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

6. August 8, 2026 at 6:59 PM UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 3, 2026 at 11:56 PM UTCinvestigating

   Estamos experimentando solicitudes lentas de manejo para Google SERP proxy. Estamos investigando el tema.

2. August 4, 2026 at 12:43 AM UTCinvestigating

   El Google SERP Proxy no está procesando casi ninguna solicitud o es muy lento. Estamos investigando el tema.

3. August 4, 2026 at 11:05 AM UTCidentified

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

4. August 5, 2026 at 1:30 PM UTCresolved

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

Traducido automáticamente desde la actualización oficial del incidente.

1. July 26, 2026 at 6:53 AM UTCinvestigating

   El modo Actor Standby tiene una tasa de error más alta y puede requerir más retries de lo habitual. Estamos investigando la causa. https://docs.apify.com/actors/running/standby

2. July 26, 2026 at 7:57 AM UTCresolved

   El problema se ha resuelto. El impacto fue un aumento de la tasa de error en la API Actor Standby, no otro componente fue afectado. No hubo tiempo de inactividad durante el período del incidente.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 2:49 PM UTCidentified

   Actualmente estamos investigando las operaciones de sincronización en nuestra API causadas por operaciones de base de datos lentas debido a cambios en los grupos.

2. July 21, 2026 at 4:43 PM UTCidentified

   Las operaciones de base de datos lentas siguen afectando nuestros sistemas. El rendimiento de la API ha mejorado, pero las carreras de Actor se están agotando debido a la reducción de la capacidad de los trabajadores.

3. July 21, 2026 at 5:11 PM UTCmonitoring

   Estamos monitoreando la situación. La capacidad del trabajador mejoró y ahora es capaz de manejar las carreras de Actor.

4. July 21, 2026 at 5:47 PM UTCinvestigating

   Nuestro rendimiento de los grupos de base de datos se ha degradado aún más, y toda la plataforma se enfrenta a una mayor eliminación. Seguiremos informando de que la situación progresa.

5. July 21, 2026 at 8:33 PM UTCidentified

   Hemos identificado la cuestión y estamos trabajando para la recuperación. El sistema está operativo, pero la capacidad está tapada, lo que da lugar a que Actor corra en el estado "listo" y una gran parte de ellos se agotan.

6. July 21, 2026 at 8:34 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

7. July 21, 2026 at 8:52 PM UTCidentified

   Los actores están ahora plenamente operativos, y el sistema está procesando todas las carreras a tiempo.

8. July 21, 2026 at 9:28 PM UTCmonitoring

   Todos los sistemas están operativos. Esperamos que la base de datos se recupere plenamente en 4 horas (1 am UTC). Estamos monitoreando el rendimiento de la plataforma. Nos disculpamos por cualquier inconveniente que esto pueda haber causado.

9. July 22, 2026 at 2:38 AM UTCresolved

   La base de datos está totalmente recuperada y todos los sistemas están operativos. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. Actualmente estamos implementando nuevas medidas para asegurar que esto no vuelva a suceder.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 21, 2026 at 6:52 AM UTCinvestigating

   Se está migrando entre servidores un número mayor que el habitual de carreras de Actor, que puede causar interrupciones breves o reiniciar para algunas carreras. Actualmente estamos investigando la cuestión.

2. July 21, 2026 at 6:57 AM UTCidentified

   Se ha identificado la causa de las migraciones elevadas de Actor. Estamos resolviendo la causa.

3. July 21, 2026 at 7:21 AM UTCmonitoring

   Se ha aplicado una solución y las migraciones de Actor corren regresan a la normalidad. Nos disculpamos por cualquier inconveniente que esto pueda haber causado. Tomamos en serio este problema y tomaremos medidas para evitar que esas cuestiones ocurran en el futuro.

4. July 21, 2026 at 11:53 AM UTCresolved

   Todos los sistemas están operativos, y nos disculpamos por cualquier inconveniente que esto pueda haber causado.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 2:04 PM UTCinvestigating

   Estamos viendo el rendimiento degradado de las solicitudes de Google SERP. Las respuestas pueden tardar más de lo habitual. Estamos investigando el tema.

2. July 17, 2026 at 8:08 PM UTCresolved

   La cuestión se ha resuelto. Tanto el tiempo de respuesta como la tasa de éxito han vuelto a niveles normales.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 4, 2026 at 3:07 PM UTCinvestigating

   We're investigating the issue.

2. June 4, 2026 at 3:29 PM UTCidentified

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

3. June 4, 2026 at 3:34 PM 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. June 4, 2026 at 5:07 PM UTCresolved

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

1. May 15, 2026 at 11:48 AM UTCinvestigating

   We're investigating the issue.

2. May 15, 2026 at 11:51 AM UTCinvestigating

   We are continuing to investigate this issue.

3. May 15, 2026 at 12:19 PM UTCmonitoring

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

4. May 16, 2026 at 5:28 AM UTCresolved

   This incident has been resolved.

1. May 14, 2026 at 8:21 AM 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. May 6, 2026 at 8:08 PM 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. May 7, 2026 at 8:27 AM UTCresolved

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

1. May 5, 2026 at 1:50 PM UTCinvestigating

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

2. May 5, 2026 at 2:19 PM UTCmonitoring

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

3. May 5, 2026 at 2:34 PM 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. May 1, 2026 at 11:23 AM 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. May 1, 2026 at 11:29 AM 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. May 1, 2026 at 11:57 AM UTCresolved

   This incident has been resolved.

1. April 29, 2026 at 12:35 PM UTCinvestigating

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

2. April 29, 2026 at 1:07 PM 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. April 29, 2026 at 1:35 PM 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. April 29, 2026 at 3:13 PM UTCresolved

   This incident has been resolved.

1. April 8, 2026 at 10:01 AM UTCinvestigating

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

2. April 8, 2026 at 6:25 PM 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. April 8, 2026 at 8:35 PM 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. April 8, 2026 at 9:16 PM 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. April 8, 2026 at 10:24 PM 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. April 9, 2026 at 9:15 AM 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. March 11, 2026 at 12:48 PM 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. March 12, 2026 at 9:34 AM UTCresolved

   This incident has been resolved.

1. March 6, 2026 at 5:27 PM 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. March 6, 2026 at 7:05 PM UTCresolved

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

1. January 27, 2026 at 4:10 AM 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. January 27, 2026 at 5:45 AM UTCmonitoring

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

3. January 27, 2026 at 9:33 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. January 27, 2026 at 9:37 AM UTCresolved

   This incident has been resolved.

1. January 21, 2026 at 3:17 PM 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. January 21, 2026 at 3:19 PM 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.