Critical incident

Apify: Degraded performance of API operations due to slow database operations

Affected: API (api.apify.com), Actors

Current status of Apify: Operational — live Apify status

Timeline

1. Jul 21, 2026, 14:49 UTC
   identified
   We are currently investigating timing out operations on our API caused by slow database operations due to cluster changes.
2. Jul 21, 2026, 16:43 UTC
   identified
   Slow database operations continue to impact our systems. API performance has improved, but Actor runs are currently timing out due to reduced worker capacity.
3. Jul 21, 2026, 17:09 UTC
   identified
   We are continuing to work on a fix for this issue.
4. Jul 21, 2026, 17:11 UTC
   monitoring
   We are now monitoring the situation. Worker capacity improved and is now able to handle starting Actor runs.
5. Jul 21, 2026, 17:47 UTC
   investigating
   Our database cluster performance has further degraded, and the whole platform is facing a major outage. We will keep informing you as the situation progresses.
6. Jul 21, 2026, 20:33 UTC
   identified
   We have identified the issue and are working towards recovery. The system is operational, but the capacity is capped, resulting in Actor runs being buffered in the "ready" state and a large portion of them timing out.
7. Jul 21, 2026, 20:34 UTC
   identified
   We are continuing to work on a fix for this issue.
8. Jul 21, 2026, 20:52 UTC
   identified
   Actors are now fully operational, and the system is processing all the runs in time.
9. Jul 21, 2026, 21:28 UTC
   monitoring
   All systems are operational. We expect the database to fully recover in 4 hours (1 am UTC). We are monitoring the platform's performance. We apologize for any inconvenience this might have caused.
10. Jul 22, 2026, 02:38 UTC
    resolved
    The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure this won't happen again.

Updates as published by Apify (original).