Apify incident

Degraded performance of API operations due to slow database operations

Critical Resolved View vendor source →

Apify experienced a critical incident on July 21, 2026 affecting API (api.apify.com) and Actors, lasting 11h 49m. The incident has been resolved; the full update timeline is below.

Started
Jul 21, 2026, 02:49 PM UTC
Resolved
Jul 22, 2026, 02:38 AM UTC
Duration
11h 49m
Detected by Pingoru
Jul 21, 2026, 02:49 PM UTC

Affected components

API (api.apify.com)Actors

Update timeline

  1. identified Jul 21, 2026, 02:49 PM UTC

    We are currently investigating timing out operations on our API caused by slow database operations due to cluster changes.

  2. identified Jul 21, 2026, 04:43 PM UTC

    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. identified Jul 21, 2026, 05:09 PM UTC

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

  4. monitoring Jul 21, 2026, 05:11 PM UTC

    We are now monitoring the situation. Worker capacity improved and is now able to handle starting Actor runs.

  5. investigating Jul 21, 2026, 05:47 PM UTC

    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. identified Jul 21, 2026, 08:33 PM UTC

    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. identified Jul 21, 2026, 08:34 PM UTC

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

  8. identified Jul 21, 2026, 08:52 PM UTC

    Actors are now fully operational, and the system is processing all the runs in time.

  9. monitoring Jul 21, 2026, 09:28 PM UTC

    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. resolved Jul 22, 2026, 02:38 AM UTC

    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.