演员运行中发生的错误
Outage重大事件
- resolved
部分演员跑道出现性能退化,起跑和结束时间较慢,出错率也较高. 这个问题已经得到解决.
自动翻译自官方事件更新。
59 Apify incidents · 2024年10月 — official updates, affected components, duration and resolution details.
部分演员跑道出现性能退化,起跑和结束时间较慢,出错率也较高. 这个问题已经得到解决.
自动翻译自官方事件更新。
我们的平台业绩正在退化。 演员可以较慢开始或超时. 如果你的演员超时,你可以让他们复活. 我们正在调查这种退化的原因,并将尽快公布最新情况.
我们已经确定了这个问题,我们正在着手恢复。 在我们解决根本问题之前,演员的表现仍然退化.
我们已经解决了根本问题,演员的表现已经恢复,我们正在监测局势。 如果你的演员超时了 你可以让他们复活.
这一事件已经得到解决.
自动翻译自官方事件更新。
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代理正在经历更多的响应时间和更高的出错率. 我们正在调查这个问题.
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.
自动翻译自官方事件更新。
Google SERP 代理服务器处理请求缓慢 我们正在调查这个问题.
Google SERP代理程序几乎不处理任何请求,或者非常缓慢. 我们正在调查这个问题.
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.
自动翻译自官方事件更新。
演员备用模式的出错率较高,可能需要比平时更多的重试. 我们正在调查原因 https://docs.apify.com/actors/running/standby 页面存档备份,存于互联网档案馆
这个问题已经得到解决。 影响是演员备用API的误差率提高,而不是其他部分受到影响. 事件发生期间没有停机时间.
自动翻译自官方事件更新。
我们目前正在调查由于集群变化导致数据库操作缓慢而导致的我国API运行的时间安排.
数据库运行缓慢继续影响我们的系统。 API的表现有所改善,但是由于工人能力下降,演员跑步目前已经到了淘汰时间.
我们现在正在监测局势。 工人能力得到提高,现在能够处理开始的演员业务.
我们的数据库集群性能进一步退化,整个平台面临重大故障. 我们会随时通知你.
我们已查明这一问题,并正在努力恢复。 该系统已投入使用,但容量被封顶,导致Actor运行被"准备"状态所缓冲,其中一大部分时间被淘汰.
我们正在继续努力解决这个问题。
演员现在已全面投入使用,系统正在及时处理所有运行.
所有系统都已投入运作。 我们预计数据库将在4小时后完全恢复(协调世界时1分)。 我们正在监测平台的表现。 我们对此可能造成的不便表示歉意.
数据库已完全恢复,所有系统已开始运作。 我们对此可能造成的不便表示歉意。 我们目前正在执行新的措施,以确保不再发生这种情况.
自动翻译自官方事件更新。
正在服务器之间迁移一个比平时更多的演员运行,这可能导致一些运行的短暂中断或重启. 我们目前正在调查这一问题.
已查明高阶演员移徙的原因。 我们正在解决问题.
已经安装了固定设备,操作者运行的迁移正在恢复正常。 我们对此可能造成的不便表示歉意。 我们认真对待这一问题,并将采取步骤来避免今后发生此类问题.
所有系统都已投入使用,我们对此可能造成的任何不便表示歉意.
自动翻译自官方事件更新。
我们看到Google SERP请求的性能下降. 答复的时间可能比通常要长。 我们正在调查这个问题.
这个问题已经得到解决。 反应时间和成功率都已恢复正常水平.
自动翻译自官方事件更新。
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.