- Level
- confirmed
- Worst impact
- Partial outage
- Components
- SERP
- Down Index
- 45of 100
What to do
Check whether you use Apify SERP. 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 1d 13h it lasted.
Anything that failed between 2026-08-03 23:56 UTC and 2026-08-05 13:30 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 experiencing slow requests handling for Google SERP proxy. We're investigating the issue.
provider
- investigating
The Google SERP Proxy is not processing almost any requests or is very slow. We're investigating the issue.
provider
- identified
The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.
provider
- resolved
The Google SERP Proxy is stabilized, and we continue to monitor its performance.
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-3b6ea5f7e6
Is Apify still down?
No, this incident was resolved 2026-08-05 13:30 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
1d 13h, from 2026-08-03 23:56 UTC to 2026-08-05 13:30 UTC, by the times Apify posted.
What was affected?
Apify named SERP.
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.