Service disruption

What to do

• Check whether you use Apify Web (apify.com), Datacenter, Dataset, Console (console.apify.com) and 8 more. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 35m it lasted.

  Anything that failed between 2025-04-10 13:04 UTC and 2025-04-10 14:39 UTC may need a replay.

• Subscribe to Apify's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=apify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Apify 5

1. monitoringApr 10, 2025, 1:04 PM UTC

   A problem with deploying new services caused a system-wide restart and 5-7 minutes long service disruption. The system has recovered after the restart, and the Actors continue operating but the performance is largely degraded.

   provider

2. investigatingApr 10, 2025, 1:28 PM UTC

   We are currently investigating this issue.

   provider

3. monitoringApr 10, 2025, 1:41 PM UTC

   A fix has been implemented and we are monitoring the results.

   provider

4. monitoringApr 10, 2025, 1:46 PM UTC

   We identified the root cause and changed the configuration to prevent this from happening again.

   provider

5. resolvedApr 10, 2025, 2:39 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.