- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Web (apify.com), AWS EC2, Datacenter, Dataset, AWS S3, Console (console.apify.com), Request queue, Residential, API (api.apify.com), AWS SQS, Key-value store, SERP, AWS ELB, Actors, AWS ElastiCache, Scheduler, Webhooks, Docs (docs.apify.com), MCP server (mcp.apify.com), AWS ECR, AWS EKS
- Down Index
- 59of 100
What to do
Check whether you use Apify Web (apify.com), AWS EC2, Datacenter, Dataset and 17 more. 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 7h 41m it lasted.
Anything that failed between 2025-10-20 07:00 UTC and 2025-10-20 14:40 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
- identified
We are currently experiencing issues accessing and using our services across the entire system. The issue originates from AWS (see: AWS Status Page https://health.aws.amazon.com/health/status). We are actively investigating and will provide updates as soon as possible.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
The upstream AWS issue is recovering, and we’re seeing full recovery across all our systems. Between 07:00–09:30 UTC, no Actor runs were executed. There was no data loss, but Actor runs during this window did not start as expected, or they may have timed out or failed. Actor schedules resumed operation at 10:00 UTC. Unfortunately, we were unable to update this status page earlier due to statuspage.io not working as well. In addition, Intercom, our customer support chat provider, was also experiencing an outage at the same time, which limited our ability to communicate in real-time. We’re deeply sorry for the lack of timely communication and the disruption this caused. We’re already reviewing our communication and redundancy processes to ensure we can keep you better informed during future incidents, even when multiple systems are affected. Thank you for your patience and understanding.
provider
- resolved
All systems are operational, and we apologize for any inconvenience this might have caused. We are currently implementing new measures to make sure that this won't happen 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-21d7c8316f
Is Apify still down?
No, this incident was resolved 2025-10-20 14:40 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
7h 41m, from 2025-10-20 07:00 UTC to 2025-10-20 14:40 UTC, by the times Apify posted.
What was affected?
Apify named Web (apify.com), AWS EC2, Datacenter, Dataset and 17 more.
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.