Forhøjede fejl i Actor-kørsler
OutageStørre hændelse
- resolved
Nogle Actor-kørsler oplevede forringet ydeevne, langsommere start og sluttider og forhøjede fejlrater. Problemet er løst.
Automatisk oversat fra den officielle hændelsesopdatering.
59 Apify incidents · oktober 2024 — official updates, affected components, duration and resolution details.
Nogle Actor-kørsler oplevede forringet ydeevne, langsommere start og sluttider og forhøjede fejlrater. Problemet er løst.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplever i øjeblikket forringet platforms ydeevne. Skuespillere kan være langsommere at starte eller time out. Hvis dine skuespillere kommer ud, kan du genoplive dem. Vi undersøger årsagen til denne nedbrydning og vil sende opdateringen så hurtigt som muligt.
Vi har identificeret problemet, og vi arbejder på genopretning. Skuespillerens præstation er stadig forringet, indtil vi løser det underliggende problem.
Vi har løst det underliggende problem, og skuespillerens resultater er kommet sig, vi overvåger nu situationen. Hvis din skuespiller løber timet ud, kan du genoplive dem.
Denne hændelse er blevet løst.
Automatisk oversat fra den officielle hændelsesopdatering.
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.
A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.
This incident has been resolved.
Google SERP proxy oplever øgede svartider og forhøjede fejlrater. Vi undersøger sagen.
The performance problems are caused by issues with our upstream providers. We are in contact with them to find a solution.
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.
The success rate and latency is continuing to improve to almost normal levels, we expect full recovery soon.
We have seen a full recovery of the SERP proxy success rates. We will continue monitoring for any future degradation.
This incident has been resolved.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplever langsomme anmodninger om håndtering af Google SERP-proxy. Vi undersøger sagen.
Google SERP Proxy behandler ikke næsten alle anmodninger eller er meget langsom. Vi undersøger sagen.
The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.
The Google SERP Proxy is stabilized, and we continue to monitor its performance.
Automatisk oversat fra den officielle hændelsesopdatering.
Actor Standby-tilstand har en højere fejlfrekvens og kan kræve flere forsøg end normalt. Vi undersøger sagen. http: / / docs.apipy.com / actors / running / standby
Problemet er løst. Virkningen var en øget fejlfrekvens ved Actor Standby API, ikke andre komponent blev påvirket. Der var ingen nedetid under hændelsen.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi er i øjeblikket ved at undersøge timing out operationer på vores API forårsaget af langsom database operationer på grund af klyngeændringer.
Slow database operationer fortsætter med at påvirke vores systemer. API performance er forbedret, men Actor kører i øjeblikket timing på grund af nedsat medarbejderkapacitet.
Vi overvåger nu situationen. Worker kapacitet forbedret og er nu i stand til at håndtere start Actor kører.
Vores database klynge ydeevne er yderligere nedbrudt, og hele platformen står over for et stort udfald. Vi vil blive ved med at informere Dem, efterhånden som situationen skrider frem.
Vi har identificeret problemet og arbejder hen imod genopretning. Systemet er operationelt, men kapaciteten er begrænset, hvilket resulterer i, at Actor kører buffered i "klar" tilstand, og en stor del af dem timing ud.
Vi fortsætter med at arbejde på en løsning på dette problem.
Skuespillere er nu fuldt operationelle, og systemet er ved at behandle alle løbene i tid.
Alle systemer er i drift. Vi forventer, at databasen til fuldt opsving i 4 timer (1 am UTC). Vi overvåger platformens præstationer. Vi undskylder for eventuelle ulemper.
Databasen er fuldt genvundet, og alle systemer er operationelle. Vi undskylder for eventuelle ulemper. Vi er i øjeblikket ved at gennemføre nye foranstaltninger for at sikre, at dette ikke sker igen.
Automatisk oversat fra den officielle hændelsesopdatering.
Et højere end normalt antal Actor-kørsler migreres mellem servere, hvilket kan forårsage korte afbrydelser eller genstarter for nogle kørsler. Vi undersøger i øjeblikket spørgsmålet.
Årsagen til den forhøjede Actor køre vandringer er blevet identificeret. Vi løser sagen.
Et fix er blevet anvendt og Actor køre vandringer vender tilbage til normal. Vi undskylder for eventuelle ulemper. Vi tager dette problem alvorligt og vil tage skridt til at undgå, at sådanne spørgsmål opstår i fremtiden.
Alle systemer er funktionsdygtige, og vi undskylder for eventuelle ulemper.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi ser forringet ydeevne i Google SERP-anmodninger. Det kan tage længere tid end normalt. Vi undersøger sagen.
Spørgsmålet er løst. Både responstid og succesrate er vendt tilbage til normale niveauer.
Automatisk oversat fra den officielle hændelsesopdatering.
We're investigating the issue.
The issue has been identified, and we are resolving it.
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.
Webhooks are operational, and we apologize for any inconvenience this might have caused.
We're investigating the issue.
We are continuing to investigate this issue.
We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.
This incident has been 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.
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.
We have implemented a fix for the OAuth flow, and the connections are now working normally.
We're experiencing outage of key-value store. We're investigation the cause of the issue
A fix has been implemented and we are monitoring the results.
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.
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.
Console UI and API performance should be back to standard levels. We will monitor the situation while we investigate the incident's root cause.
This incident has been resolved.
We're experiencing degraded performance. We're investigation the cause of the issue
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.
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.
This incident has been resolved.
We are investigating slow API response times due to underlying database issues.
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.
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.
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.
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.
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.
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
This incident has been resolved.
We are currently experiencing degraded performance of the datacenter proxy. The root cause has been identified and we are working on a fix.
Datacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused.
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.
The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.
We are continuing to monitor for any further issues.
This incident has been resolved.