- Level
- confirmed
- Worst impact
- Major outage
- Components
- Actors, Scheduler
- Regions
- us
- Down Index
- 59of 100
What to do
Check whether you use Apify Actors, Scheduler in us. 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 8h 47m it lasted.
Anything that failed between 2025-10-20 22:43 UTC and 2025-10-21 07:30 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 7
- identified
We're experiencing degraded performance in Actor runs due an upstream issue with AWS EC2. See: AWS Status Page https://health.aws.amazon.com/health/status
provider
- identified
The upstream issue with AWS EC2 is ongoing, resulting in significant degradation of Actor performance. We are closely monitoring the situation and implementing a limited set of mitigation measures where possible. Further updates will be provided as they become available.
provider
- identified
We are experiencing a significant disruption in running Actors due to an ongoing upstream issue with AWS EC2. Our team is actively monitoring the situation and will restore full service as soon as possible. The integrity of the data on the platform has not been compromised.
provider
- identified
We're seeing slow recovery across our systems from the global AWS outage. You should be able to run your Actors but schedules remain non-operational.
provider
- identified
We can confirm AWS is slowly recovering to a normal state. We have been able to recover all the Apify services fully and as the last step we turned scheduler back on. As this was a second disruption within a day we will keep monitoring the situation over night. We will identify and take steps to improve the reaction next time, however we can't ensure Apify platform staying fully operational when underlying provider (AWS) experiences complete outage.
provider
- monitoring
We can confirm AWS is slowly recovering to a normal state. We have been able to recover all the Apify services fully and as the last step we turned scheduler back on. As this was a second disruption within a day we will keep monitoring the situation over night. We will identify and take steps to improve the reaction next time, however we can't ensure Apify platform staying fully operational when underlying provider (AWS) experiences complete outage.
provider
- resolved
As of 07:30 UTC, the Apify platform is operating normally. Amazon Web Services have also marked their incident as resolved, which gives us confidence that the outage has concluded. We will continue to monitor the situation and apologize for any inconvenience this may have 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-a3dee74436
Is Apify still down?
No, this incident was resolved 2025-10-21 07:30 UTC. For Apify's live state, see https://down.guide/apify.
How long did it last?
8h 47m, from 2025-10-20 22:43 UTC to 2025-10-21 07:30 UTC, by the times Apify posted.
What was affected?
Apify named Actors, Scheduler in us.
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.