- Level
- confirmed
- Worst impact
- Degraded
- Components
- Residential
- Down Index
- 33of 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 5h 27m it lasted.
Anything that failed between 2026-01-27 04:10 UTC and 2026-01-27 09:37 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 4
- investigating
We are currently investigating an issue affecting residential proxies. Some requests are failing or timing out. Our team is actively working to identify the root cause and restore normal operation. Further updates will be provided as we learn more.
provider
- monitoring
The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.
provider
- monitoring
We are continuing to monitor for any further issues.
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-5f0a3a46fc
Is Apify still down?
No, this incident was resolved 2026-01-27 09:37 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
5h 27m, from 2026-01-27 04:10 UTC to 2026-01-27 09:37 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.