Apify incident

Degraded Actor runs performance

Critical Resolved View vendor source →

Apify experienced a critical incident on October 20, 2025 affecting Actors and Scheduler, lasting 8h 46m. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 10:43 PM UTC
Resolved
Oct 21, 2025, 07:30 AM UTC
Duration
8h 46m
Detected by Pingoru
Oct 20, 2025, 10:43 PM UTC

Affected components

ActorsScheduler

Update timeline

  1. identified Oct 20, 2025, 02:42 PM UTC

    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

  2. identified Oct 20, 2025, 03:51 PM UTC

    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.

  3. identified Oct 20, 2025, 04:16 PM UTC

    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.

  4. identified Oct 20, 2025, 08:59 PM UTC

    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.

  5. identified Oct 20, 2025, 10:40 PM UTC

    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.

  6. monitoring Oct 20, 2025, 10:43 PM UTC

    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.

  7. resolved Oct 21, 2025, 07:46 AM UTC

    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.