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.
Posted Apr 09, 2026 - 11:15 CEST
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.
Posted Apr 09, 2026 - 00:24 CEST
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.
Posted Apr 08, 2026 - 23:16 CEST
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.
Posted Apr 08, 2026 - 22:35 CEST
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.
Posted Apr 08, 2026 - 20:25 CEST
Investigating
We are investigating slow API response times due to underlying database issues.
Posted Apr 08, 2026 - 12:01 CEST
This incident affected: Console (console.apify.com), API (api.apify.com), and Actors.