- Level
- confirmed
- Worst impact
- Degraded
- Components
- SERP
- Down Index
- 33of 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 6h 4m it lasted.
Anything that failed between 2026-07-17 14:04 UTC and 2026-07-17 20:08 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
- investigating
We're seeing degraded performance of Google SERP requests. Responses may take longer than usual. We're investigating the issue.
provider
- resolved
The issue has been resolved. Both the response time and success rate have returned to normal levels.
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-f77d01673f
Is Apify still down?
No, this incident was resolved 2026-07-17 20:08 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
6h 4m, from 2026-07-17 14:04 UTC to 2026-07-17 20:08 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.