Apify Outage History

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

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 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.

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.

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.

We are currently experiencing degraded performance of the datacenter proxy. The root cause has been identified and we are working on a fix.

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.

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.

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 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.

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 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.

Actors cannot be built due to the Docker Hub authentication outage. For more details, see: https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9 Actor runs are unaffected, and all existing builds can be run as usual.

We are monitoring the situation and waiting for a fix on the Docker Hub side.

We have identified the issue and implemented a fix. New Actor builds (created after 11:20 UTC) are now working correctly. We are working on fixing the affected Actor builds created between 10:50 UTC and 11:20 UTC.

We are experiencing an increased error rate for Actor runs on some nodes. A small percentage is affected. We identified a potential root cause and are working towards a resolution.

We want to inform you that country codes for datacenter proxies are currently not working as expected. For now, please use datacenter proxies without specifying country codes to ensure uninterrupted service. We're actively working on resolving this issue and will update you as soon as it's fixed. Thank you for your understanding and patience!