Histórico de interrupções do Apify

1. 20 Eost 2026 da 14:05 UTCinvestigating

   Atualmente estamos experimentando desempenho de plataforma degradada. Os atores podem ser mais lentos para começar ou parar. Se os teus actores se afastarem, podes ressuscitá-los. Estamos a investigar a causa desta degradação e vamos publicar a actualização o mais rapidamente possível.

2. 20 Eost 2026 da 14:49 UTCidentified

   Identificámos a questão e estamos a trabalhar na recuperação. O desempenho do ator ainda está degradado até resolvermos o problema subjacente.

3. 20 Eost 2026 da 15:20 UTCmonitoring

   Resolvemos a questão subjacente e o desempenho do Actor recuperou, estamos agora a acompanhar a situação. Se o teu ator correr o tempo, podes ressuscitá-los.

4. 20 Eost 2026 da 16:14 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

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

   This incident has been resolved.

1. 7 Eost 2026 da 21:00 UTCinvestigating

   O proxy do Google SERP está tendo aumento dos tempos de resposta e taxas de erro elevadas. Estamos a investigar a questão.

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

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

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

   This incident has been resolved.

Traduzido automaticamente da atualização oficial do incidente.

1. 3 Eost 2026 da 23:56 UTCinvestigating

   Estamos passando por solicitações lentas para o proxy do Google SERP. Estamos a investigar a questão.

2. 4 Eost 2026 da 00:43 UTCinvestigating

   O Google SERP Proxy não está processando quase nenhum pedido ou é muito lento. Estamos a investigar a questão.

3. 4 Eost 2026 da 11:05 UTCidentified

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

4. 5 Eost 2026 da 13:30 UTCresolved

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

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Gouere 2026 da 06:53 UTCinvestigating

   O modo de espera do ator tem uma taxa de erro mais alta e pode exigir mais tentativas do que o habitual. Estamos a investigar a causa. https://docs.apify.com/actors/running/standby

2. 26 Gouere 2026 da 07:57 UTCresolved

   O problema foi resolvido. O impacto foi uma taxa de erro aumentada na API Ator Standby, não outro componente foi afetado. Não houve paralisação durante o período do incidente.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 14:49 UTCidentified

   Atualmente estamos investigando operações de timing para fora em nossa API causadas por operações de banco de dados lentos devido a alterações de cluster.

2. 21 Gouere 2026 da 16:43 UTCidentified

   Operações lentas de banco de dados continuam impactando nossos sistemas. O desempenho da API melhorou, mas as execuções do ator estão atualizando devido à capacidade reduzida do trabalhador.

3. 21 Gouere 2026 da 17:11 UTCmonitoring

   Estamos agora a acompanhar a situação. A capacidade do trabalhador melhorou e agora é capaz de lidar com a partida Ator executa.

4. 21 Gouere 2026 da 17:47 UTCinvestigating

   Nosso desempenho de cluster de banco de dados degrada-se ainda mais, e toda a plataforma está enfrentando uma grande falha. Continuaremos a informar-vos à medida que a situação avança.

5. 21 Gouere 2026 da 20:33 UTCidentified

   Identificámos a questão e estamos a trabalhar no sentido da recuperação. O sistema está operacional, mas a capacidade é limitada, resultando em Ator corre sendo tamponado no estado "pronto" e uma grande parte deles cronometrando.

6. 21 Gouere 2026 da 20:34 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

7. 21 Gouere 2026 da 20:52 UTCidentified

   Os actores estão agora totalmente operacionais, e o sistema está a processar todas as operações a tempo.

8. 21 Gouere 2026 da 21:28 UTCmonitoring

   Todos os sistemas estão operacionais. Esperamos que o banco de dados se recupere totalmente em 4 horas (1 em UTC). Estamos monitorando o desempenho da plataforma. Pedimos desculpa por qualquer inconveniente que isto possa ter causado.

9. 22 Gouere 2026 da 02:38 UTCresolved

   A base de dados está totalmente recuperada e todos os sistemas estão operacionais. Pedimos desculpa por qualquer inconveniente que isto possa ter causado. Estamos actualmente a implementar novas medidas para garantir que isto não volte a acontecer.

Traduzido automaticamente da atualização oficial do incidente.

1. 21 Gouere 2026 da 06:52 UTCinvestigating

   Um número maior que o usual de execução do ator está sendo migrado entre servidores, o que pode causar breves interrupções ou reiniciar algumas execuções. Estamos neste momento a investigar a questão.

2. 21 Gouere 2026 da 06:57 UTCidentified

   A causa das migrações elevadas do Ator foi identificada. Estamos a resolver a causa.

3. 21 Gouere 2026 da 07:21 UTCmonitoring

   Uma correção foi aplicada e migrações de execução do ator estão retornando ao normal. Pedimos desculpa por qualquer inconveniente que isto possa ter causado. Levamos este problema a sério e tomaremos medidas para evitar que tais questões ocorram no futuro.

4. 21 Gouere 2026 da 11:53 UTCresolved

   Todos os sistemas estão operacionais, e pedimos desculpa por qualquer inconveniente que isto possa ter causado.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 14:04 UTCinvestigating

   Estamos vendo desempenho degradado dos pedidos do Google SERP. As respostas podem demorar mais do que o habitual. Estamos a investigar a questão.

2. 17 Gouere 2026 da 20:08 UTCresolved

   A questão foi resolvida. Tanto o tempo de resposta como a taxa de sucesso retornaram aos níveis normais.

Traduzido automaticamente da atualização oficial do incidente.

1. 4 Mezheven 2026 da 15:07 UTCinvestigating

   We're investigating the issue.

2. 4 Mezheven 2026 da 15:29 UTCidentified

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

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

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

1. 15 Mae 2026 da 11:48 UTCinvestigating

   We're investigating the issue.

2. 15 Mae 2026 da 11:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 15 Mae 2026 da 12:19 UTCmonitoring

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

4. 16 Mae 2026 da 05:28 UTCresolved

   This incident has been resolved.

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

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

1. 5 Mae 2026 da 13:50 UTCinvestigating

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

2. 5 Mae 2026 da 14:19 UTCmonitoring

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

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

   This incident has been resolved.

1. 29 Ebrel 2026 da 12:35 UTCinvestigating

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

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

   This incident has been resolved.

1. 8 Ebrel 2026 da 10:01 UTCinvestigating

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

2. 8 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Ebrel 2026 da 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 Meurzh 2026 da 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 Meurzh 2026 da 09:34 UTCresolved

   This incident has been resolved.

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

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

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

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

3. 27 Genver 2026 da 09:33 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 27 Genver 2026 da 09:37 UTCresolved

   This incident has been resolved.

1. 21 Genver 2026 da 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 Genver 2026 da 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.