- Level
- confirmed
- Worst impact
- Degraded
- Components
- SERP
- Down Index
- 35of 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 10d 23h it lasted.
Anything that failed between 2025-01-16 15:34 UTC and 2025-01-27 14:56 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 5
- identified
SERP proxies' performance has degraded because of problems with external data providers. We are working on a fix to restore the success rate to its original level.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- identified
We have identified the problem and are working towards fixing the performance. For now, we will keep experiencing more retries and degraded performance.
provider
- monitoring
A fix has been implemented, and we are back to the usual performance.
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-d0e1a02505
Is Apify still down?
No, this incident was resolved 2025-01-27 14:56 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
10d 23h, from 2025-01-16 15:34 UTC to 2025-01-27 14:56 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.