- Level
- confirmed
- Worst impact
- Major outage
- Apify says
- about 5m
- Down Index
- 41of 100
What to do
Check whether your product depends on Apify. 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 0m it lasted.
Anything that failed between 2026-05-14 07:20 UTC and 2026-05-14 07:20 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.
Root cause
We experienced degraded performance on our proxy due to an unexpected increase in load.Read the postmortem
Updates from Apify 1
- resolved
We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally. We apologize for the inconvenience.
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-2faa436a1b
Is Apify still down?
No, this incident was resolved 2026-05-14 07:20 UTC. For Apify's live state, see https://down.guide/providers/apify.
How long did it last?
0m, from 2026-05-14 07:20 UTC to 2026-05-14 07:20 UTC, by the times Apify posted.
What caused it?
Apify wrote: "We experienced degraded performance on our proxy due to an unexpected increase in load." The postmortem: https://stspg.io/wxq0p0mj2b2j
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.