- Level
- confirmed
- Worst impact
- Degraded
- Components
- API (api.apify.com)
- Down Index
- 30of 100
What to do
Check whether you use Apify API (api.apify.com). 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 15m it lasted.
Anything that failed between 2025-10-29 19:06 UTC and 2025-10-29 20:21 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
- identified
The Actor run endpoint stopped returning `stats` attribute, which is a breaking change, especially for pay-per-event Actors using Python SDK. We've identified the issue and are working on a fix.
provider
- identified
The Actor run endpoint issue has been resolved. The `stats` attribute is now returned correctly, and Actor runs should be fully operational.
provider
- resolved
This incident has been resolved.
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-c755bb79a5
Is Apify still down?
No, this incident was resolved 2025-10-29 20:21 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
1h 15m, from 2025-10-29 19:06 UTC to 2025-10-29 20:21 UTC, by the times Apify posted.
What was affected?
Apify named API (api.apify.com).
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.