Database replica down

What to do

• Check whether you use Apify Dataset, Console (console.apify.com), Request queue, API (api.apify.com) and 4 more. Check your stack

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

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

  Anything that failed between 2025-08-01 06:30 UTC and 2025-08-01 08:13 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 4

1. investigatingAug 1, 2025, 6:30 AM UTC

   One of our database replicas is currently down. Our engineering team is investigating the root cause and working to restore full redundancy. All core services remain operational, but you may experience slightly degraded performance during this time. We’ll provide an update as soon as we have more information.

   provider

2. investigatingAug 1, 2025, 6:50 AM UTC

   We are continuing to investigate this issue.

   provider

3. monitoringAug 1, 2025, 7:01 AM UTC

   We have identified the root cause of the issue affecting one of our database replicas and have applied a fix. The system remained operational throughout the incident. However, there were a few brief disruptions—lasting only a few seconds—during which running actors were restarted. We are sorry for the inconvenience. We will continue to monitor the system to ensure the situation remains stabilized.

   provider

4. resolvedAug 1, 2025, 8:13 AM UTC

   This incident has been resolved. We are sorry for the inconvenience.

   provider

Corrections

None so far.

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