- 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 13h 42m it lasted.
Anything that failed between 2025-03-06 00:10 UTC and 2025-03-06 13:52 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 currently investigating this issue.
provider
- identified
The incident is caused by issues with our proxy providers. We are actively working with them to resolve the issue and will provide updates as soon as we have more information.
provider
- monitoring
A fix has been implemented to channel most of the traffic through the most reliable proxy providers. However, results for the shopping tab might still return content in unexpected languages due to a geolocation issue. We're aware of this and are working on a solution.
provider
- resolved
The incident has been resolved and SERP is fully functional again.
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-40a023189a
Is Apify still down?
No, this incident was resolved 2025-03-06 13:52 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
13h 42m, from 2025-03-06 00:10 UTC to 2025-03-06 13:52 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.