Apify incident

Apify API Degraded Performance

Major Resolved View vendor source →

Apify experienced a major incident on April 8, 2026 affecting Console (console.apify.com) and API (api.apify.com) and 1 more component, lasting 23h 14m. The incident has been resolved; the full update timeline is below.

Started
Apr 08, 2026, 10:01 AM UTC
Resolved
Apr 09, 2026, 09:15 AM UTC
Duration
23h 14m
Detected by Pingoru
Apr 08, 2026, 10:01 AM UTC

Affected components

Console (console.apify.com)API (api.apify.com)Actors

Update timeline

  1. investigating Apr 08, 2026, 10:01 AM UTC

    We are investigating slow API response times due to underlying database issues.

  2. identified Apr 08, 2026, 06:25 PM UTC

    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.

  3. investigating Apr 08, 2026, 08:35 PM UTC

    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.

  4. identified Apr 08, 2026, 09:16 PM UTC

    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.

  5. monitoring Apr 08, 2026, 10:24 PM UTC

    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.

  6. resolved Apr 09, 2026, 09:15 AM UTC

    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.