Apify Outage History

Started Oct 20, 2025, 02:42 PM UTC· resolved Oct 21, 2025, 07:30 AM UTC

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.

Read the full incident report →

Started Oct 20, 2025, 07:00 AM UTC· resolved Oct 20, 2025, 02:40 PM UTC

1. 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.

2. identified Oct 20, 2025, 09:45 AM UTC

   We are continuing to work on a fix for this issue.

3. 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.

4. 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.

Read the full incident report →

Started Oct 14, 2025, 04:35 PM UTC· resolved Oct 14, 2025, 04:37 PM UTC

1. investigating Oct 14, 2025, 04:35 PM UTC

   Documentation page is not loading properly from 15:20 UTC. We are currently investigating this issue.

2. resolved Oct 14, 2025, 04:37 PM UTC

   Incident has been resolved

Read the full incident report →

Started Sep 24, 2025, 11:16 PM UTC· resolved Sep 25, 2025, 01:48 AM UTC

1. identified Sep 24, 2025, 11:16 PM UTC

   Actors cannot be built due to the Docker Hub authentication outage. For more details, see: https://www.dockerstatus.com/pages/incident/533c6539221ae15e3f000031/68d47a2f93c09e05486d93a9 Actor runs are unaffected, and all existing builds can be run as usual.

2. identified Sep 24, 2025, 11:16 PM UTC

   We are monitoring the situation and waiting for a fix on the Docker Hub side.

3. monitoring Sep 25, 2025, 01:15 AM UTC

   DockerHub has deployed a fix, and we’re seeing recovery in the Actor build success rate. We continue to monitor the situation.

4. resolved Sep 25, 2025, 01:48 AM UTC

   Actor build success rate has fully recovered. If your Actor builds failed, please rerun them. We apologize for any inconvenience caused.

Read the full incident report →

Started Sep 15, 2025, 11:50 AM UTC· resolved Sep 15, 2025, 12:05 PM UTC

1. resolved Sep 15, 2025, 12:38 PM UTC

   The latest version of the apify/send-mail Actor failed to email all recipients. The issue lasted from around 13:50 to 14:05 CEST. The root cause was identified, and the service of the Actor was restored. We apologize for any inconvenience this might have caused. We take this problem seriously and will take steps to prevent such issues from occurring in the future.

Read the full incident report →

Started Sep 09, 2025, 11:17 AM UTC· resolved Sep 09, 2025, 03:06 PM UTC

1. investigating Sep 09, 2025, 11:17 AM UTC

   If you create a new build of an Actor and try to run it, the Actor run fails to start. Old builds are not affected. We are currently investigating this issue and will provide updates as we continue.

2. identified Sep 09, 2025, 11:37 AM UTC

   We have identified the issue and implemented a fix. New Actor builds (created after 11:20 UTC) are now working correctly. We are working on fixing the affected Actor builds created between 10:50 UTC and 11:20 UTC.

3. resolved Sep 09, 2025, 03:06 PM UTC

   All affected Actors have been rebuilt, and all builds are working correctly now. We will continue to monitor the situation in case more failed builds appear.

Read the full incident report →

Started Aug 07, 2025, 02:44 PM UTC· resolved Aug 07, 2025, 04:15 PM UTC

1. identified Aug 07, 2025, 02:44 PM UTC

   We are experiencing an increased error rate for Actor runs on some nodes. A small percentage is affected. We identified a potential root cause and are working towards a resolution.

2. monitoring Aug 07, 2025, 03:01 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 07, 2025, 04:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 01, 2025, 09:03 AM UTC· resolved Aug 01, 2025, 01:21 PM UTC

1. identified Aug 01, 2025, 09:03 AM UTC

   We want to inform you that country codes for datacenter proxies are currently not working as expected. For now, please use datacenter proxies without specifying country codes to ensure uninterrupted service. We're actively working on resolving this issue and will update you as soon as it's fixed. Thank you for your understanding and patience!

2. resolved Aug 01, 2025, 01:21 PM UTC

   The issue with country codes for datacenter proxies has been resolved. Datacenter proxies with country codes are now fully operational again. We apologize for any inconvenience this may have caused, and thank you for your patience!

Read the full incident report →

Started Aug 01, 2025, 06:30 AM UTC· resolved Aug 01, 2025, 08:13 AM UTC

1. investigating Aug 01, 2025, 06:30 AM UTC

   One of our database replicas is currently down. Our engineering team is investigating the root cause and working to restore full redundancy. All core services remain operational, but you may experience slightly degraded performance during this time. We’ll provide an update as soon as we have more information.

2. investigating Aug 01, 2025, 06:50 AM UTC

   We are continuing to investigate this issue.

3. monitoring Aug 01, 2025, 07:01 AM UTC

   We have identified the root cause of the issue affecting one of our database replicas and have applied a fix. The system remained operational throughout the incident. However, there were a few brief disruptions—lasting only a few seconds—during which running actors were restarted. We are sorry for the inconvenience. We will continue to monitor the system to ensure the situation remains stabilized.

4. resolved Aug 01, 2025, 08:13 AM UTC

   This incident has been resolved. We are sorry for the inconvenience.

Read the full incident report →

Started Jun 10, 2025, 09:00 AM UTC· resolved Jun 11, 2025, 07:20 AM UTC

1. resolved Jun 10, 2025, 09:00 AM UTC

   From 23:30 to 7:20 UTC, the platform experienced a slight increase in Actor failure rates. As of 7:20 UTC, the issue has been resolved. We estimate that approximately 70 Actor runs were affected. If your Actor run failed with the message "We've encountered an unexpected system error.", you can resurrect it. We apologize for any inconvenience this may have caused.

Read the full incident report →

Started Jun 03, 2025, 12:16 AM UTC· resolved Jun 03, 2025, 05:21 AM UTC

1. investigating Jun 03, 2025, 12:16 AM UTC

   We're experiencing degraded performance on our API due to an increase in load on the API. We're investigating the problem.

2. identified Jun 03, 2025, 12:30 AM UTC

   Performance has recovered, and we are investigating the root cause.

3. monitoring Jun 03, 2025, 12:42 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jun 03, 2025, 05:21 AM UTC

   All systems are operational now. Between 1:00 a.m. and 2:00 a.m. (CET), we experienced a high load on our platform, which may have led to degraded performance and slowed down our services during that timeframe. The error caused a data duplication resulting in a ~30 of users being overcharged by 10 USD on average, and some of the storage and run statistics were duplicated. The underlying issue has been addressed and we’ll be contacting and refunding the impacted users.

Read the full incident report →

Started May 24, 2025, 06:23 AM UTC· resolved May 24, 2025, 07:57 AM UTC

1. investigating May 24, 2025, 06:23 AM UTC

   The automated QA system incorrectly flagged some Actors published in the Apify Store as "Under maintenance" due to a system error, causing a false positive test result. No issues were detected in the Actors' actual runtime behavior. As a creator of these Actors, you can ignore the alerts. This only affected Actors published in the Apify Store.

2. identified May 24, 2025, 06:50 AM UTC

   The issue has been identified and a fix is being implemented.

3. resolved May 24, 2025, 07:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 22, 2025, 04:54 AM UTC· resolved Apr 22, 2025, 01:48 PM UTC

1. investigating Apr 22, 2025, 04:54 AM UTC

   We are experiencing degraded performance of multiple platform services and restarts of various system components. We have just stabilized the system and are looking for the root cause of this slowdown.

2. identified Apr 22, 2025, 04:58 AM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Apr 22, 2025, 05:28 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Apr 22, 2025, 01:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 10, 2025, 01:04 PM UTC· resolved Apr 10, 2025, 02:39 PM UTC

1. monitoring Apr 10, 2025, 01:04 PM UTC

   A problem with deploying new services caused a system-wide restart and 5-7 minutes long service disruption. The system has recovered after the restart, and the Actors continue operating but the performance is largely degraded.

2. investigating Apr 10, 2025, 01:28 PM UTC

   We are currently investigating this issue.

3. monitoring Apr 10, 2025, 01:41 PM UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring Apr 10, 2025, 01:46 PM UTC

   We identified the root cause and changed the configuration to prevent this from happening again.

5. resolved Apr 10, 2025, 02:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 16, 2025, 01:46 AM UTC· resolved Mar 16, 2025, 10:55 AM UTC

1. identified Mar 16, 2025, 01:46 AM UTC

   Since 00:10 UTC, the Google SERP proxy has experienced increased response times. This may cause requests using the proxy to time out. As a temporary workaround, we recommend increasing the request timeout. We apologize for any inconvenience and are working toward a swift resolution.

2. resolved Mar 16, 2025, 10:55 AM UTC

   We have implemented a fix, and the response time has been recovering since 09:30 UTC. As of 10:30 UTC, the response time has returned to normal. We will continue to monitor the response time. We apologize for any inconvenience caused.

Read the full incident report →

Started Mar 06, 2025, 08:45 PM UTC· resolved Mar 06, 2025, 08:53 PM UTC

1. investigating Mar 06, 2025, 08:45 PM UTC

   We are currently investigating this issue.

2. resolved Mar 06, 2025, 08:53 PM UTC

   The incident was swiftly resolved on the side of ur SERP proxy providers. All services are functional again

Read the full incident report →

Started Mar 06, 2025, 12:10 AM UTC· resolved Mar 06, 2025, 01:52 PM UTC

1. investigating Mar 06, 2025, 12:49 AM UTC

   We are currently investigating this issue.

2. identified Mar 06, 2025, 01:48 AM UTC

   The incident is caused by issues with our proxy providers. We are actively working with them to resolve the issue and will provide updates as soon as we have more information.

3. monitoring Mar 06, 2025, 02:39 AM UTC

   A fix has been implemented to channel most of the traffic through the most reliable proxy providers. However, results for the shopping tab might still return content in unexpected languages due to a geolocation issue. We're aware of this and are working on a solution.

4. resolved Mar 06, 2025, 01:52 PM UTC

   The incident has been resolved and SERP is fully functional again.

Read the full incident report →

Started Feb 28, 2025, 09:45 AM UTC· resolved Feb 28, 2025, 12:01 PM UTC

1. identified Feb 28, 2025, 09:45 AM UTC

   The issue has been identified and a fix is being implemented.

2. identified Feb 28, 2025, 09:59 AM UTC

   - Users who subscribe or upgrade their account to a higher tier did not receive invoices for the upgrade, and the subscription plan was not updated. - Subscriptions wasn't upgraded correctly. - There is no service disruption for existing subscriptions. - We are working towards a fix, and invoices will be reissued and subscriptions upgraded once the fix is deployed.

3. monitoring Feb 28, 2025, 10:26 AM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Feb 28, 2025, 12:01 PM UTC

   Invoices issuing and subscribing is fully operational again.

Read the full incident report →

Started Feb 24, 2025, 03:24 PM UTC· resolved Feb 24, 2025, 04:55 PM UTC

1. investigating Feb 24, 2025, 03:24 PM UTC

   We're experiencing issues with scheduling. Some Actor runs may not start in time. We are identifying potentially started duplicate Actor runs. The first problems started around 11:00 CET at a very small scale and escalated around 3:00 UTC. The performance of API is partially degraded, and some endpoints might be answering slower than usual. We're investigating the issue and will keep you informed about the progress. We are sorry for the inconvenience caused; this is a critical issue. In response to the incident, we aborted some of the runs in the ready state. This affects runs that were started by the scheduler or another way from 2025-02-24 15:00 UTC. These runs can be resurrected if needed.

2. investigating Feb 24, 2025, 03:59 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 24, 2025, 04:22 PM UTC

   We have identified the root cause and deployed a fix. Both API and Actor components are now stable, and we’re slowly starting the scheduled runs.

4. resolved Feb 24, 2025, 04:55 PM UTC

   Summary: We experienced a partial outage of the scheduler and degraded performance of Apify API. Timeframe: The issue started at a small scale from 11.00 UTC and then escalated around 15.00 UTC. By 16.15 UTC, the issue was resolved. Impact: - During the incident, some scheduled Actors did not start or were run twice. - In response, we've aborted some of the runs that started after 15:00 UTC and turned off the Schedule component for approximately 45 minutes. - If your runs were aborted, they can now be safely resurrected; see: https://docs.apify.com/platform/actors/running/runs-and-builds#resurrection-of-finished-run - There was no data loss for runs in progress, but some runs were not triggered. - API performance was degraded at various levels along the incident, and some runs started via API may have been in a READY state for longer than usual. We're sorry for the inconvenience. We take this issue seriously and will implement measures to mitigate similar issues in the future. We will provide a post-mortem summary here with more details later this week.

5. postmortem Feb 26, 2025, 02:26 PM UTC

   Malfunctioning scheduler post-mortem Date of incident: 2025-02-24 Duration: 10:30 UTC - 16:15 UTC Impact: * From 10:30 UTC to 15:00 UTC, some of the schedules were triggered more than once. It started as a small-scale issue, and the problem escalated after 14:00 UTC. * From 15:00 UTC to 15:55 UTC, API performance was degraded, and some Actor builds and runs were stuck in the READY state. Some Actor runs were aborted but can be resurrected. * From 15:25 UTC to 16:15 UTC, schedules were not working, so some Actor runs did not start at all. What happened? * We implemented a change that would improve Actor startup performance by targeting Docker layers more effectively. * The change caused certain database items to increase in size, overloading the network of the primary cluster and leading to degraded performance. * Some core components, including those behind the scheduler, repeatedly went out of memory. What we did * We temporarily paused the Actor run scheduler and manually aborted runs triggered after 15:00 UTC. * We downscaled the platform to make the database responsive again and reverted the change causing the bug. Next steps * We will improve our monitoring to catch similar problems, deviations, and network spikes sooner before they escalate. * We will investigate the component's current architecture to ensure we prevent such incidents in the future. We apologize for the disruption and appreciate your patience. If you have any questions, please reach out to [[email protected]](mailto:[email protected]). Sincerely, Apify engineering team

Read the full incident report →

Started Feb 22, 2025, 10:12 PM UTC· resolved Feb 22, 2025, 11:38 PM UTC

1. investigating Feb 22, 2025, 10:12 PM UTC

   We are investigating the issue.

2. investigating Feb 22, 2025, 10:13 PM UTC

   We are continuing to investigate this issue.

3. identified Feb 22, 2025, 11:05 PM UTC

   We've identified the cause of the issue and are taking steps to resolve it.

4. monitoring Feb 22, 2025, 11:25 PM UTC

   A fix has been implemented and we're monitoring the results. It might take some time to allocate all jobs, until all services have fully recovered. We're sorry for the inconvenience. We will implement new measures based on this critical incident to prevent similar incidents in the future.

5. monitoring Feb 22, 2025, 11:33 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Feb 22, 2025, 11:38 PM UTC

   This incident has been resolved.

7. postmortem Feb 26, 2025, 02:21 PM UTC

   Saturday outage post-mortem Date of incident: 2025-02-22 Impact: * Complete downtime of the Apify platform from 22.00 UTC to 23.00 UTC. * No Actors could be started. * Those already running were paused and continued running after the incident was resolved. * There was no data loss, but the workloads were disrupted. What happened: * Our user base is growing fast, and the number of new signups is increasing exponentially. The exponentially increased load revealed suboptimalities that had not manifested before. * One misconfigured query then caused a peak in memory due to a load of a suboptimal index, which caused the cluster to crash. What we did: * The cluster size was increased to ensure enough memory until the issue was fixed. * Then, the cluster and all the dependent systems were restarted. Next steps: * We are already re-architecting our primary database clusters to optimize systems for future growth. * As part of this, we aim to decrease the size of all our clusters to ensure performant restarts in case of a problem. * We are currently optimizing indexing and querying among heavy-load components. * In addition, we identified missing metrics that would indicate similar problems ahead of time. We sincerely apologize for the disruption and appreciate your patience. If you have any questions, please reach out to [[email protected]](mailto:[email protected]). Sincerely, Apify engineering team

Read the full incident report →

Started Jan 16, 2025, 03:34 PM UTC· resolved Jan 27, 2025, 02:56 PM UTC

1. identified Jan 16, 2025, 03:34 PM UTC

   SERP proxies' performance has degraded because of problems with external data providers. We are working on a fix to restore the success rate to its original level.

2. identified Jan 17, 2025, 07:56 AM UTC

   We are continuing to work on a fix for this issue.

3. identified Jan 17, 2025, 09:03 AM UTC

   We have identified the problem and are working towards fixing the performance. For now, we will keep experiencing more retries and degraded performance.

4. monitoring Jan 17, 2025, 10:42 AM UTC

   A fix has been implemented, and we are back to the usual performance.

5. resolved Jan 27, 2025, 02:56 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 16, 2025, 01:47 PM UTC· resolved Jan 16, 2025, 01:51 PM UTC

1. investigating Jan 16, 2025, 01:47 PM UTC

   Google SERP proxy may experiencing outage. We're currently investigating an issue.

2. resolved Jan 16, 2025, 01:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 16, 2025, 01:15 PM UTC· resolved Jan 16, 2025, 01:17 PM UTC

1. investigating Jan 16, 2025, 01:15 PM UTC

   Google SERP proxy may experiencing outage. We're currently investigating an issue.

2. resolved Jan 16, 2025, 01:17 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 08, 2024, 08:49 PM UTC· resolved Dec 08, 2024, 08:53 PM UTC

1. identified Dec 08, 2024, 08:49 PM UTC

   We have identified an issue on the apify.com website. Every page crashes right after it's loaded, and we're working on fixing this as soon as possible.

2. identified Dec 08, 2024, 08:52 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved Dec 08, 2024, 08:53 PM UTC

   We successfully deployed the fix and apify.com should be operational now.

Read the full incident report →