Attualmente stiamo sperimentando le prestazioni della piattaforma degradata. Gli attori possono essere più lenti per iniziare o tempo libero. Se i tuoi Attori si allontanano, puoi resuscitarli. Stiamo indagando sulla causa di questo degrado e pubblicheremo l'aggiornamento il prima possibile.
identified
Abbiamo identificato il problema e stiamo lavorando al recupero. Le prestazioni dell'Attore sono ancora degradate fino a quando non risolviamo il problema sottostante.
monitoring
Abbiamo risolto il problema sottostante e le prestazioni dell'Attore sono state recuperate, stiamo monitorando la situazione. Se il tuo Attore esegue il tempo, puoi resuscitarli.
resolved
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Degraded performance of SHADER proxy group
Inizio 13 agosto 2026 alle ore 15:38 UTC · 22h 26m
IssuesIncidente minore
Componenti interessati
Datacenter
identified
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.
monitoring
A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.
resolved
This incident has been resolved.
Prestazioni degradate di Google SERP Proxy
Inizio 7 agosto 2026 alle ore 21:00 UTC · 21h 59m
IssuesIncidente minore
Componenti interessati
SERP
investigating
Il proxy SERP di Google sta vivendo un aumento dei tempi di risposta e tassi di errore elevati. Stiamo indagando sul problema.
identified
The performance problems are caused by issues with our upstream providers. We are in contact with them to find a solution.
identified
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.
identified
The success rate and latency is continuing to improve to almost normal levels, we expect full recovery soon.
monitoring
We have seen a full recovery of the SERP proxy success rates. We will continue monitoring for any future degradation.
resolved
This incident has been resolved.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Google SERP Il proxy non funziona
Inizio 3 agosto 2026 alle ore 23:56 UTC · 1d 13h
OutageIncidente maggiore
Componenti interessati
SERP
investigating
Stiamo sperimentando richieste lente di gestione per Google SERP proxy. Stiamo indagando sul problema.
investigating
Il proxy Google SERP non elabora quasi tutte le richieste o è molto lento. Stiamo indagando sul problema.
identified
The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.
resolved
The Google SERP Proxy is stabilized, and we continue to monitor its performance.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Aumento del tasso di errore sugli endpoint Actor Standby
Inizio 26 luglio 2026 alle ore 06:53 UTC · 1h 4m
IssuesIncidente minore
Componenti interessati
Actors
investigating
La modalità Actor Standby ha un tasso di errore più elevato e può richiedere più ripetizioni del solito. Stiamo indagando sulla causa.
https://docs.apify.com/actors/running/standby
resolved
Il problema è stato risolto. L'impatto è stato un aumento del tasso di errore all'Actor Standby API, non altri componenti sono stati colpiti. Non c'era tempo di fermo durante il periodo dell'incidente.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Prestazioni degradate delle operazioni API a causa di operazioni lento database
Inizio 21 luglio 2026 alle ore 14:49 UTC · 11h 49m
OutageIncidente critico
Componenti interessati
API (api.apify.com)Actors
identified
Attualmente stiamo indagando sulle operazioni di time out sulla nostra API causate da operazioni di database lenti a causa di modifiche del cluster.
identified
Le operazioni del database lento continuano a influenzare i nostri sistemi. Le prestazioni dell'API sono migliorate, ma le corse dell'Attore sono attualmente in fase di stazionamento a causa della ridotta capacità del lavoratore.
monitoring
Ora stiamo monitorando la situazione. Capacità di lavoro migliorata e ora è in grado di gestire le corse di Actor di partenza.
investigating
Le nostre prestazioni del cluster di database sono ulteriormente degradate, e l'intera piattaforma sta affrontando un importante outage.
Continueremo a informarvi mentre la situazione progredisce.
identified
Abbiamo identificato il problema e stiamo lavorando per il recupero. Il sistema è operativo, ma la capacità è bloccata, con conseguente Actor viene tamponato nello stato "pronto" e una gran parte di loro tempi out.
identified
Stiamo continuando a lavorare per risolvere questo problema.
identified
Gli attori sono ora pienamente operativi, e il sistema sta elaborando tutte le operazioni in tempo.
monitoring
Tutti i sistemi sono operativi. Ci aspettiamo che il database di recuperare completamente in 4 ore (1 am UTC).
Stiamo monitorando le prestazioni della piattaforma. Ci scusiamo per qualsiasi inconveniente che possa aver causato.
resolved
Il database è completamente recuperato e tutti i sistemi sono operativi. Ci scusiamo per qualsiasi inconveniente che possa aver causato. Attualmente stiamo implementando nuove misure per garantire che questo non accada di nuovo.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Alto numero di migrazioni di Actor run
Inizio 21 luglio 2026 alle ore 06:52 UTC · 5h 1m
IssuesIncidente minore
Componenti interessati
Actors
investigating
Un numero più alto di solito di Actor viene migrato tra i server, che possono causare brevi interruzioni o riavvio per alcune piste. Stiamo indagando sul problema.
identified
La causa delle elevate migrazioni di Actor run è stata identificata. Stiamo risolvendo la causa.
monitoring
Una correzione è stata applicata e le migrazioni di Actor run stanno tornando alla normalità. Ci scusiamo per qualsiasi inconveniente che possa aver causato. Prendiamo seriamente questo problema e prenderemo misure per evitare tali problemi che si verificano in futuro.
resolved
Tutti i sistemi sono operativi, e ci scusiamo per qualsiasi inconveniente che potrebbe aver causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Prestazioni SERP degradate
Inizio 17 luglio 2026 alle ore 14:04 UTC · 6h 4m
IssuesIncidente minore
Componenti interessati
SERP
investigating
Stiamo vedendo le prestazioni degradate delle richieste di Google SERP. Le risposte possono richiedere più tempo del solito. Stiamo indagando sul problema.
resolved
Il problema è stato risolto.
Sia il tempo di risposta che il tasso di successo sono tornati a livelli normali.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Degraded performance of webhooks
Inizio 4 giugno 2026 alle ore 15:07 UTC · 2h 0m
IssuesIncidente minore
Componenti interessati
Webhooks
investigating
We're investigating the issue.
identified
The issue has been identified, and we are resolving it.
monitoring
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.
resolved
Webhooks are operational, and we apologize for any inconvenience this might have caused.
Degraded performance of API, Console, and Proxy
Inizio 15 maggio 2026 alle ore 11:48 UTC · 17h 40m
IssuesIncidente minore
Componenti interessati
API (api.apify.com)Console (console.apify.com)DatacenterResidentialSERP
investigating
We're investigating the issue.
investigating
We are continuing to investigate this issue.
monitoring
We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.
resolved
This incident has been resolved.
Proxy degradation
Inizio 14 maggio 2026 alle ore 05:20 UTC · 2h 0m
OutageIncidente critico
resolved
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.
MCP: Failing OAuth sing-in from clients using CIMD with loopback redirects
Inizio 6 maggio 2026 alle ore 20:08 UTC · 12h 18m
IssuesIncidente minore
Componenti interessati
MCP server (mcp.apify.com)
identified
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.
resolved
We have implemented a fix for the OAuth flow, and the connections are now working normally.
Outage of Key-value store
Inizio 5 maggio 2026 alle ore 13:50 UTC · 45m
OutageIncidente critico
Componenti interessati
Console (console.apify.com)
investigating
We're experiencing outage of key-value store. We're investigation the cause of the issue
monitoring
A fix has been implemented and we are monitoring the results.
resolved
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.
Degraded Console UI and API performance
Inizio 1 maggio 2026 alle ore 11:23 UTC · 33m
IssuesIncidente minore
Componenti interessati
API (api.apify.com)Console (console.apify.com)
identified
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.
monitoring
Console UI and API performance should be back to standard levels.
We will monitor the situation while we investigate the incident's root cause.
resolved
This incident has been resolved.
Outage of API and Actors
Inizio 29 aprile 2026 alle ore 12:35 UTC · 2h 38m
OutageIncidente maggiore
Componenti interessati
API (api.apify.com)Console (console.apify.com)Actors
investigating
We're experiencing degraded performance. We're investigation the cause of the issue
investigating
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.
investigating
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.
resolved
This incident has been resolved.
Apify API Degraded Performance
Inizio 8 aprile 2026 alle ore 10:01 UTC · 23h 15m
OutageIncidente maggiore
Componenti interessati
API (api.apify.com)Console (console.apify.com)Actors
investigating
We are investigating slow API response times due to underlying database issues.
identified
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.
investigating
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.
identified
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.
monitoring
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.
resolved
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.
Security Incident Notification – March 6, 2026
Inizio 11 marzo 2026 alle ore 12:48 UTC · 20h 46m
Pending
Componenti interessati
General
monitoring
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
resolved
This incident has been resolved.
Degraded Datacenter Proxy Performance
Inizio 6 marzo 2026 alle ore 17:27 UTC · 1h 37m
IssuesIncidente minore
Componenti interessati
Datacenter
identified
We are currently experiencing degraded performance of the datacenter proxy.
The root cause has been identified and we are working on a fix.
resolved
Datacenter proxy performance has been fully restored.
We apologize for any inconvenience this may have caused.
Degraded residential proxy performance
Inizio 27 gennaio 2026 alle ore 04:10 UTC · 5h 27m
IssuesIncidente minore
Componenti interessati
Residential
investigating
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.
monitoring
The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved.
Apify Console temporarily unvailable
Inizio 21 gennaio 2026 alle ore 15:17 UTC · 2m
OutageIncidente critico
Componenti interessati
Console (console.apify.com)
identified
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.
resolved
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.