- Level
- confirmed
- Worst impact
- Degraded
- Components
- SERP
- Down Index
- 34of 100
What to do
Check whether you use Apify SERP. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 9h 9m it lasted.
Anything that failed between 2025-03-16 01:46 UTC and 2025-03-16 10:55 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
- identified
Since 00:10 UTC, the Google SERP proxy has experienced increased response times. This may cause requests using the proxy to time out. As a temporary workaround, we recommend increasing the request timeout. We apologize for any inconvenience and are working toward a swift resolution.
provider
- resolved
We have implemented a fix, and the response time has been recovering since 09:30 UTC. As of 10:30 UTC, the response time has returned to normal. We will continue to monitor the response time. We apologize for any inconvenience caused.
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-1f15e44bd0
Is Apify still down?
No, this incident was resolved 2025-03-16 10:55 UTC. For Apify's live state, see https://down.guide/providers/apify.
How long did it last?
9h 9m, from 2025-03-16 01:46 UTC to 2025-03-16 10:55 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.