- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Console (console.apify.com), API (api.apify.com), Actors
- Down Index
- 46of 100
What to do
Check whether you use Apify Console (console.apify.com), API (api.apify.com), Actors. 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 23h 15m it lasted.
Anything that failed between 2026-04-08 10:01 UTC and 2026-04-09 09:15 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 6
- investigating
We are investigating slow API response times due to underlying database issues.
provider
- identified
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.
provider
- investigating
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.
provider
- identified
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.
provider
- monitoring
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.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2af40d537f
Is Apify still down?
No, this incident was resolved 2026-04-09 09:15 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
23h 15m, from 2026-04-08 10:01 UTC to 2026-04-09 09:15 UTC, by the times Apify posted.
What was affected?
Apify named Console (console.apify.com), API (api.apify.com), Actors.
What caused it?
Apify hasn't published a root cause. If it does, it shows here.
Where does this come from?
Apify's official status page, https://status.apify.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.