Apify experienced a major incident on October 20, 2025 affecting Web (apify.com) and AWS EC2 and 1 more component, lasting 7h 40m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Oct 20, 2025, 09:45 AM UTC
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.
- identified Oct 20, 2025, 09:45 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Oct 20, 2025, 09:54 AM UTC
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.
- resolved Oct 20, 2025, 02:40 PM UTC
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.