- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Actors
- Down Index
- 42of 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 3h 49m it lasted.
Anything that failed between 2025-09-09 11:17 UTC and 2025-09-09 15:06 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 3
- investigating
If you create a new build of an Actor and try to run it, the Actor run fails to start. Old builds are not affected. We are currently investigating this issue and will provide updates as we continue.
provider
- identified
We have identified the issue and implemented a fix. New Actor builds (created after 11:20 UTC) are now working correctly. We are working on fixing the affected Actor builds created between 10:50 UTC and 11:20 UTC.
provider
- resolved
All affected Actors have been rebuilt, and all builds are working correctly now. We will continue to monitor the situation in case more failed builds appear.
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-e3486020fa
Is Apify still down?
No, this incident was resolved 2025-09-09 15:06 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
3h 49m, from 2025-09-09 11:17 UTC to 2025-09-09 15:06 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.