Elevated errors in Actor runs
Timeline · 1 update
- resolved Sep 22, 2026, 03:06 PM UTC
Some Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved.
Apify Outage History
Apify is up right nowApify had 50 outages in the last 2 years totaling 160h 59m of downtime — averaging 2.1 incidents per month.
There were 50 Apify outages since December 3, 2024 totaling 160h 59m of downtime. Each is summarised below — incident details, duration, and resolution information.
Degraded Actor performance
Affected: Actors
Timeline · 4 updates
- investigating Aug 20, 2026, 02:05 PM UTC
We are currently experiencing degraded platform performance. Actors can be slower to start or time out. If your Actors time out, you can resurrect them. We are investigating the cause of this degradation and will post the update as soon as possible.
- identified Aug 20, 2026, 02:49 PM UTC
We have identified the issue and we are working on recovery. The Actor performance is still degraded until we resolve the underlying issue.
- monitoring Aug 20, 2026, 03:20 PM UTC
We have resolved the underlying issue and the Actor performance has recovered, we are now monitoring the situation. If your Actor runs timed out, you can resurrect them.
- resolved Aug 20, 2026, 04:14 PM UTC
This incident has been resolved.
Degraded performance of SHADER proxy group
Affected: Datacenter
Timeline · 3 updates
- identified Aug 13, 2026, 03:38 PM UTC
We are seeing elevated error rates on the SHADER proxy group connected with issues with one of our upstream providers. If you use this proxy group directly (not through the virtual AUTO proxy group), please switch to using another group (such as BUYPROXIES94952) temporarily.
- monitoring Aug 13, 2026, 08:08 PM UTC
A fix has been implemented upstream and the SHADER proxy group has recovered. We continue monitoring the situation for any further disruption.
- resolved Aug 14, 2026, 02:05 PM UTC
This incident has been resolved.
Degraded performance of Google SERP Proxy
Affected: SERP
Timeline · 6 updates
- investigating Aug 07, 2026, 09:00 PM UTC
The Google SERP proxy is experiencing increased response times and elevated error rates. We are investigating the issue.
- identified Aug 08, 2026, 10:18 AM UTC
The performance problems are caused by issues with our upstream providers. We are in contact with them to find a solution.
- identified Aug 08, 2026, 10:19 AM UTC
We have applied partial fixes to improve the situation and lower the error rate. We are still seeing an elevated error rate and are continuing to work on reaching a full resolution.
- identified Aug 08, 2026, 01:36 PM UTC
The success rate and latency is continuing to improve to almost normal levels, we expect full recovery soon.
- monitoring Aug 08, 2026, 06:58 PM UTC
We have seen a full recovery of the SERP proxy success rates. We will continue monitoring for any future degradation.
- resolved Aug 08, 2026, 06:59 PM UTC
This incident has been resolved.
Increased error rate on Actor Standby endpoints
Affected: Actors
Timeline · 2 updates
- investigating Jul 26, 2026, 06:53 AM UTC
Actor Standby mode has a higher error rate and may require more retries than usual. We are investigating the cause. https://docs.apify.com/actors/running/standby
- resolved Jul 26, 2026, 07:57 AM UTC
The problem has been resolved. Impact was an increased error rate at the Actor Standby API, not other component was affected. There was no downtime during the period of the incident.
Degraded performance of API operations due to slow database operations
Affected: API (api.apify.com)Actors
Timeline · 10 updates
High number of Actor run migrations
Affected: Actors
Timeline · 4 updates
- investigating Jul 21, 2026, 06:52 AM UTC
A higher-than-usual number of Actor runs are being migrated between servers, which may cause brief interruptions or restarts for some runs. We are currently investigating the issue.
- identified Jul 21, 2026, 06:57 AM UTC
The cause of the elevated Actor run migrations has been identified. We are resolving the cause.
- monitoring Jul 21, 2026, 07:21 AM UTC
A fix has been applied and Actor run migrations are returning to normal. We apologize for any inconvenience this might have caused. We take this problem seriously and will be taking steps to avoid such issues occurring in the future.
- resolved Jul 21, 2026, 11:53 AM UTC
All systems are operational, and we apologize for any inconvenience this might have caused.
Degraded SERP performance
Affected: SERP
Timeline · 2 updates
- investigating Jul 17, 2026, 02:04 PM UTC
We're seeing degraded performance of Google SERP requests. Responses may take longer than usual. We're investigating the issue.
- resolved Jul 17, 2026, 08:08 PM UTC
The issue has been resolved. Both the response time and success rate have returned to normal levels.
Degraded performance of webhooks
Affected: Webhooks
Timeline · 4 updates
- investigating Jun 04, 2026, 03:07 PM UTC
We're investigating the issue.
- identified Jun 04, 2026, 03:29 PM UTC
The issue has been identified, and we are resolving it.
- monitoring Jun 04, 2026, 03:34 PM UTC
We have identified and resolved the root cause of the issue. No data loss occurred, as all webhooks are automatically retried. A backlog of pending webhooks remains and is currently being processed. We are monitoring the situation closely.
- resolved Jun 04, 2026, 05:07 PM UTC
Webhooks are operational, and we apologize for any inconvenience this might have caused.
Degraded performance of API, Console, and Proxy
Affected: DatacenterConsole (console.apify.com)ResidentialAPI (api.apify.com)SERP
Timeline · 4 updates
- investigating May 15, 2026, 11:48 AM UTC
We're investigating the issue.
- investigating May 15, 2026, 11:51 AM UTC
We are continuing to investigate this issue.
- monitoring May 15, 2026, 12:19 PM UTC
We have identified and resolved the current problems with our in-memory cache. We're monitoring the situation.
- resolved May 16, 2026, 05:28 AM UTC
This incident has been resolved.
Proxy degradation
Timeline · 1 update
- resolved May 14, 2026, 08:21 AM UTC
We experienced degraded performance on our proxy due to an unexpected increase in load. This caused slower response times for some users. The issue lasted approximately 5 minutes and has been fully resolved. All systems are now operating normally. We apologize for the inconvenience.
MCP: Failing OAuth sing-in from clients using CIMD with loopback redirects
Affected: MCP server (mcp.apify.com)
Timeline · 2 updates
- identified May 06, 2026, 08:08 PM UTC
OAuth sign-in to mcp.apify.com from clients using CIMD with loopback redirects (currently Claude Code) is failing due to a regression. Existing connections and other clients (claude.ai, Cursor, Codex) are unaffected (the later use DCR). We are sorry for the inconvenience and working on a fix.
- resolved May 07, 2026, 08:27 AM UTC
We have implemented a fix for the OAuth flow, and the connections are now working normally.
Outage of Key-value store
Affected: Console (console.apify.com)
Timeline · 3 updates
- investigating May 05, 2026, 01:50 PM UTC
We're experiencing outage of key-value store. We're investigation the cause of the issue
- monitoring May 05, 2026, 02:19 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2026, 02:34 PM UTC
We've resolved an issue where a key-value store API update caused some Actor runs to time out. If your Actor run timed out you can get it back by resurrecting it. There was no data loss. We sincerely apologize for any inconvenience this may have caused.
Degraded Console UI and API performance
Affected: Console (console.apify.com)API (api.apify.com)
Timeline · 3 updates
- identified May 01, 2026, 11:23 AM UTC
We have identified an issue causing degraded performance in the Console UI and in some API requests. We have implemented a fix, and the performance should stabilize soon.
- monitoring May 01, 2026, 11:29 AM UTC
Console UI and API performance should be back to standard levels. We will monitor the situation while we investigate the incident's root cause.
- resolved May 01, 2026, 11:57 AM UTC
This incident has been resolved.
Outage of API and Actors
Affected: Console (console.apify.com)API (api.apify.com)Actors
Timeline · 4 updates
- investigating Apr 29, 2026, 12:35 PM UTC
We're experiencing degraded performance. We're investigation the cause of the issue
- investigating Apr 29, 2026, 01:07 PM UTC
We're experiencing a full outage of Actors and API. Actors might not be starting. Our engineering team is investigating the root cause of the issue.
- investigating Apr 29, 2026, 01:35 PM UTC
We've identified the root cause of the issue, and our engineering team is monitoring the metrics. Console, Actors, and API should be stable now.
- resolved Apr 29, 2026, 03:13 PM UTC
This incident has been resolved.
Apify API Degraded Performance
Affected: Console (console.apify.com)API (api.apify.com)Actors
Timeline · 6 updates
- investigating Apr 08, 2026, 10:01 AM UTC
We are investigating slow API response times due to underlying database issues.
- identified Apr 08, 2026, 06:25 PM UTC
We’ve identified the root cause and have resolved a part of the issue, but the system has not yet fully stabilized. The Actor Runs list endpoint (https://api.apify.com/v2/acts/:actorId/runs) remains the most impacted, along with related views in the Apify Console, where we are still actively working on a fix. Additional endpoints may also experience degraded performance. At this time, we cannot provide an estimate for full resolution.
- investigating Apr 08, 2026, 08:35 PM UTC
Our systems are currently experiencing a major disruption. We sincerely apologize and are actively investigating the root cause. We will provide updates as more information becomes available.
- identified Apr 08, 2026, 09:16 PM UTC
Service has partially recovered, and we are currently experiencing degraded performance. We are actively investigating the issue and working on a fix. We will continue to provide updates as more information becomes available.
- monitoring Apr 08, 2026, 10:24 PM UTC
The Apify platform is fully recovered. The incident followed a database cluster sharding procedure that resulted in a performance impact on some operations. There was no data loss. The Actor run list API endpoint experienced performance issues between 10:00 and 20:30 UTC, followed by a partial outage of all services from 20:30 to 21:10. Now everything is back to normal, and we are monitoring the situation. We are sorry for any inconvenience caused.
- resolved Apr 09, 2026, 09:15 AM 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.
Security Incident Notification – March 6, 2026
Affected: General
Timeline · 2 updates
Degraded Datacenter Proxy Performance
Affected: Datacenter
Timeline · 2 updates
- identified Mar 06, 2026, 05:27 PM UTC
We are currently experiencing degraded performance of the datacenter proxy. The root cause has been identified and we are working on a fix.
- resolved Mar 06, 2026, 07:05 PM UTC
Datacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused.
Degraded residential proxy performance
Affected: Residential
Timeline · 4 updates
- investigating Jan 27, 2026, 04:10 AM UTC
We are currently investigating an issue affecting residential proxies. Some requests are failing or timing out. Our team is actively working to identify the root cause and restore normal operation. Further updates will be provided as we learn more.
- monitoring Jan 27, 2026, 05:45 AM UTC
The issue has been identified and a fix has been implemented. We are monitoring the system for further issues.
- monitoring Jan 27, 2026, 09:33 AM UTC
We are continuing to monitor for any further issues.
- resolved Jan 27, 2026, 09:37 AM UTC
This incident has been resolved.
Apify Console temporarily unvailable
Affected: Console (console.apify.com)
Timeline · 2 updates
- identified Jan 21, 2026, 03:17 PM UTC
Apify Console is temporarily unavailable. We have identified the issue and are rolling out the fix. There is no data loss associated with this outage and Actor runs should not be affected.
- resolved Jan 21, 2026, 03:19 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.
apify.com/store disrupted
Affected: Web (apify.com)
Timeline · 2 updates
- identified Jan 12, 2026, 08:22 AM UTC
There has been a disruption of an Apify Stoire page at apify.com. Fix is being applied, you can use Apify Store within Apify Console meanwhile - https://console.apify.com/store.
- resolved Jan 12, 2026, 08:58 AM UTC
A fix has been implemented, and Apify Store is back to normal operations.
Customer support chat unavailable
Affected: Web (apify.com)Console (console.apify.com)
Timeline · 2 updates
- monitoring Jan 09, 2026, 08:26 PM UTC
Our customer support service provider, Intercom, is currently experiencing a complete system outage. As a result, the support button in the bottom-right corner of our website may be unavailable or experience degraded performance. We apologize for the inconvenience and kindly ask you to email [email protected] for the time being.
- resolved Jan 09, 2026, 09:13 PM UTC
This incident has been resolved.
Degraded perfromance of residential proxy network
Affected: Residential
Timeline · 3 updates
- investigating Dec 31, 2025, 10:31 AM UTC
We are experiencing a higher error rate than usual for some domains and countries. We are investigating the issue.
- monitoring Dec 31, 2025, 10:41 AM UTC
We have identified the cause, and the proxy network has recovered. We are monitoring the situation.
- resolved Dec 31, 2025, 10:50 AM UTC
This incident has been resolved.
Creating new Actors from Actor templates in UI is unavailable
Affected: Console (console.apify.com)
Timeline · 3 updates
- investigating Dec 11, 2025, 02:56 PM UTC
We are currently experiencing an issue affecting the creation of new Actors from Actor templates, starting from 2:30 PM UTC. Our team is actively investigating the problem. All other platform functionality — including running existing Actors and working with them — remains unaffected.
- identified Dec 11, 2025, 04:29 PM UTC
We have identified that the issue is caused by an ongoing GitHub incident. For more details and real-time updates, please refer to the GitHub status page. We will keep you informed of any further developments.
- resolved Dec 11, 2025, 05:26 PM UTC
The issue affecting the creation of new Actors from Actor templates has now been fully resolved. Service is operating normally again.
Unintended breaking change in Actor run API endpoint
Affected: API (api.apify.com)
Timeline · 3 updates
- identified Oct 29, 2025, 07:06 PM UTC
The Actor run endpoint stopped returning `stats` attribute, which is a breaking change, especially for pay-per-event Actors using Python SDK. We've identified the issue and are working on a fix.
- identified Oct 29, 2025, 08:06 PM UTC
The Actor run endpoint issue has been resolved. The `stats` attribute is now returned correctly, and Actor runs should be fully operational.
- resolved Oct 29, 2025, 08:21 PM UTC
This incident has been resolved.