Histórico de interrupções do Apify

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 security@apify.com 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.

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.

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.

There has been a disruption of an Apify Stoire page at apify.com. Fix is being applied, you can use Apify Store within Apify Console meanwhile - https://console.apify.com/store.

A fix has been implemented, and Apify Store is back to normal operations.

Our customer support service provider, Intercom, is currently experiencing a complete system outage. As a result, the support button in the bottom-right corner of our website may be unavailable or experience degraded performance. We apologize for the inconvenience and kindly ask you to email support@apify.com for the time being.

This incident has been resolved.

We are experiencing a higher error rate than usual for some domains and countries. We are investigating the issue.

We have identified the cause, and the proxy network has recovered. We are monitoring the situation.

This incident has been resolved.

We are currently experiencing an issue affecting the creation of new Actors from Actor templates, starting from 2:30 PM UTC. Our team is actively investigating the problem. All other platform functionality — including running existing Actors and working with them — remains unaffected.

We have identified that the issue is caused by an ongoing GitHub incident. For more details and real-time updates, please refer to the GitHub status page. We will keep you informed of any further developments.

The issue affecting the creation of new Actors from Actor templates has now been fully resolved. Service is operating normally again.

The Actor run endpoint stopped returning `stats` attribute, which is a breaking change, especially for pay-per-event Actors using Python SDK. We've identified the issue and are working on a fix.

The Actor run endpoint issue has been resolved. The `stats` attribute is now returned correctly, and Actor runs should be fully operational.

This incident has been resolved.

We're experiencing degraded performance in Actor runs due an upstream issue with AWS EC2. See: AWS Status Page https://health.aws.amazon.com/health/status

The upstream issue with AWS EC2 is ongoing, resulting in significant degradation of Actor performance. We are closely monitoring the situation and implementing a limited set of mitigation measures where possible. Further updates will be provided as they become available.

We are experiencing a significant disruption in running Actors due to an ongoing upstream issue with AWS EC2. Our team is actively monitoring the situation and will restore full service as soon as possible. The integrity of the data on the platform has not been compromised.

We're seeing slow recovery across our systems from the global AWS outage. You should be able to run your Actors but schedules remain non-operational.

We can confirm AWS is slowly recovering to a normal state. We have been able to recover all the Apify services fully and as the last step we turned scheduler back on. As this was a second disruption within a day we will keep monitoring the situation over night. We will identify and take steps to improve the reaction next time, however we can't ensure Apify platform staying fully operational when underlying provider (AWS) experiences complete outage.

We can confirm AWS is slowly recovering to a normal state. We have been able to recover all the Apify services fully and as the last step we turned scheduler back on. As this was a second disruption within a day we will keep monitoring the situation over night. We will identify and take steps to improve the reaction next time, however we can't ensure Apify platform staying fully operational when underlying provider (AWS) experiences complete outage.

As of 07:30 UTC, the Apify platform is operating normally. Amazon Web Services have also marked their incident as resolved, which gives us confidence that the outage has concluded. We will continue to monitor the situation and apologize for any inconvenience this may have caused.

We are currently experiencing issues accessing and using our services across the entire system. The issue originates from AWS (see: AWS Status Page https://health.aws.amazon.com/health/status). We are actively investigating and will provide updates as soon as possible.

We are continuing to work on a fix for this issue.

The upstream AWS issue is recovering, and we’re seeing full recovery across all our systems. Between 07:00–09:30 UTC, no Actor runs were executed. There was no data loss, but Actor runs during this window did not start as expected, or they may have timed out or failed. Actor schedules resumed operation at 10:00 UTC. Unfortunately, we were unable to update this status page earlier due to statuspage.io not working as well. In addition, Intercom, our customer support chat provider, was also experiencing an outage at the same time, which limited our ability to communicate in real-time. We’re deeply sorry for the lack of timely communication and the disruption this caused. We’re already reviewing our communication and redundancy processes to ensure we can keep you better informed during future incidents, even when multiple systems are affected. Thank you for your patience and understanding.

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.

Documentation page is not loading properly from 15:20 UTC. We are currently investigating this issue.

Incident has been resolved