- Level
- confirmed
- Worst impact
- Degraded
- Components
- Actors
- Down Index
- 20of 100
What to do
Check whether you use Apify 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 0m it lasted.
Anything that failed between 2025-06-10 09:00 UTC and 2025-06-10 09:00 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 1
- resolved
From 23:30 to 7:20 UTC, the platform experienced a slight increase in Actor failure rates. As of 7:20 UTC, the issue has been resolved. We estimate that approximately 70 Actor runs were affected. If your Actor run failed with the message "We've encountered an unexpected system error.", you can resurrect it. We apologize for any inconvenience this may have caused.
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-1dbd363f9a
Is Apify still down?
No, this incident was resolved 2025-06-10 09:00 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
0m, from 2025-06-10 09:00 UTC to 2025-06-10 09:00 UTC, by the times Apify posted.
What was affected?
Apify named 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.