- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Datacenter
- Down Index
- 43of 100
What to do
Check whether you use Apify Datacenter. 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 4h 18m it lasted.
Anything that failed between 2025-08-01 09:03 UTC and 2025-08-01 13: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 2
- identified
We want to inform you that country codes for datacenter proxies are currently not working as expected. For now, please use datacenter proxies without specifying country codes to ensure uninterrupted service. We're actively working on resolving this issue and will update you as soon as it's fixed. Thank you for your understanding and patience!
provider
- resolved
The issue with country codes for datacenter proxies has been resolved. Datacenter proxies with country codes are now fully operational again. We apologize for any inconvenience this may have caused, and thank you for your patience!
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-f2b72ffecd
Is Apify still down?
No, this incident was resolved 2025-08-01 13:21 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
4h 18m, from 2025-08-01 09:03 UTC to 2025-08-01 13:21 UTC, by the times Apify posted.
What was affected?
Apify named Datacenter.
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.