Apify incident

System outage

Critical Resolved View vendor source →

Apify experienced a critical incident on November 27, 2024 affecting Datacenter and Dataset and 1 more component, lasting 2h 3m. The incident has been resolved; the full update timeline is below.

Started
Nov 27, 2024, 07:38 AM UTC
Resolved
Nov 27, 2024, 09:42 AM UTC
Duration
2h 3m
Detected by Pingoru
Nov 27, 2024, 07:38 AM UTC

Affected components

DatacenterDatasetConsole (console.apify.com)Request queueResidentialAPI (api.apify.com)Key-value storeSERPActorsScheduler

Update timeline

  1. investigating Nov 27, 2024, 07:38 AM UTC

    Due to an internal database issue, the whole platform is overloaded, and most requests are failing.

  2. monitoring Nov 27, 2024, 08:10 AM UTC

    A fix has been implemented and the platform is recovering. We will do an analysis of the impact and determine the appropriate remediation.

  3. resolved Nov 27, 2024, 09:42 AM UTC

    The incident has been resolved. It was caused by a bug with database updates under high load. Between 7:30 UTC and 8:10 UTC, the Apify platform was overloaded, and most operations were timing out or failing. This includes API calls, running Actors, proxy requests, or accessing the Console. There has been no data loss. Scheduled Actors were executed with a delay once the platform recovered. The dates of last modifications of request queues might not be fully up-to-date.