- Level
- confirmed
- Worst impact
- Degraded
- Components
- Datacenter
- Down Index
- 35of 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 22h 26m it lasted.
Anything that failed between 2026-08-13 15:38 UTC and 2026-08-14 14:05 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
We are seeing elevated error rates on the SHADER proxy group connected with issues with one of our upstream providers. If you use this proxy group directly (not through the virtual AUTO proxy group), please switch to using another group (such as BUYPROXIES94952) temporarily.
provider
- monitoring
A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.
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-f5d13fece4
Is Apify still down?
No, this incident was resolved 2026-08-14 14:05 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
22h 26m, from 2026-08-13 15:38 UTC to 2026-08-14 14:05 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.