- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Residential
- Down Index
- 37of 100
What to do
Check whether you use Apify Residential. 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 18m it lasted.
Anything that failed between 2025-12-31 10:31 UTC and 2025-12-31 10:50 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
We are experiencing a higher error rate than usual for some domains and countries. We are investigating the issue.
provider
- monitoring
We have identified the cause, and the proxy network has recovered. We are monitoring the situation.
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-d43c4338f3
Is Apify still down?
No, this incident was resolved 2025-12-31 10:50 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
18m, from 2025-12-31 10:31 UTC to 2025-12-31 10:50 UTC, by the times Apify posted.
What was affected?
Apify named Residential.
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.