Apify Outage History
Apify is up right nowPingoru has recorded 50 incidents for Apify: 25 in the last 12 months and 5 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 26 of 720 (4%) |
| May 2026 | 5 | 31 of 744 (4%) |
| June 2026 | 1 | 2 of 720 (0%) |
| July 2026 | 4 | 24 of 744 (3%) |
| August 2026 | 4 | 82 of 744 (11%) |
| September 2026 | 1 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 6 (0%) |
Incidents, newest first
Major September 22, 2026 Elevated errors in Actor runs –
Started Sep 22, 2026, 02:30 PM UTC· resolved Sep 22, 2026, 02:30 PM UTC
- resolved Sep 22, 2026, 02:30 PM UTC
Some Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved.
Notice August 20, 2026 Degraded Actor performance 2h 8m Actors
Started Aug 20, 2026, 02:05 PM UTC· resolved Aug 20, 2026, 04:14 PM UTC
- 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.
Minor August 13, 2026 Degraded performance of SHADER proxy group 22h 26m Datacenter
Started Aug 13, 2026, 03:38 PM UTC· resolved Aug 14, 2026, 02:05 PM UTC
- 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.
Minor August 7, 2026 Degraded performance of Google SERP Proxy 21h 59m SERP
Started Aug 07, 2026, 09:00 PM UTC· resolved Aug 08, 2026, 06:59 PM UTC
- 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 07, 2026, 11:00 PM 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, 06:15 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, 02:15 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.
Major August 3, 2026 Degraded performance of Google SERP Proxy 1d 13h SERP
Started Aug 03, 2026, 11:56 PM UTC· resolved Aug 05, 2026, 01:30 PM UTC
- investigating Aug 03, 2026, 11:56 PM UTC
We are experiencing slow requests handling for Google SERP proxy. We're investigating the issue.
- investigating Aug 04, 2026, 12:43 AM UTC
The Google SERP Proxy is not processing almost any requests or is very slow. We're investigating the issue.
- identified Aug 04, 2026, 11:05 AM UTC
The Google SERP proxy is working, but with slower-than-usual response times. We continue to investigate the issue.
- resolved Aug 05, 2026, 01:30 PM UTC
The Google SERP Proxy is stabilized, and we continue to monitor its performance.
Minor July 26, 2026 Increased error rate on Actor Standby endpoints 1h 4m Actors
Started Jul 26, 2026, 06:53 AM UTC· resolved Jul 26, 2026, 07:57 AM UTC
- 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.
Critical July 21, 2026 Degraded performance of API operations due to slow database operations 11h 49m API (api.apify.com), Actors
Started Jul 21, 2026, 02:49 PM UTC· resolved Jul 22, 2026, 02:38 AM UTC
- identified Jul 21, 2026, 02:49 PM UTC
We are currently investigating timing out operations on our API caused by slow database operations due to cluster changes.
- identified Jul 21, 2026, 04:43 PM UTC
Slow database operations continue to impact our systems. API performance has improved, but Actor runs are currently timing out due to reduced worker capacity.
- identified Jul 21, 2026, 05:09 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jul 21, 2026, 05:11 PM UTC
We are now monitoring the situation. Worker capacity improved and is now able to handle starting Actor runs.
- investigating Jul 21, 2026, 05:47 PM UTC
Our database cluster performance has further degraded, and the whole platform is facing a major outage. We will keep informing you as the situation progresses.
- identified Jul 21, 2026, 08:33 PM UTC
We have identified the issue and are working towards recovery. The system is operational, but the capacity is capped, resulting in Actor runs being buffered in the "ready" state and a large portion of them timing out.
- identified Jul 21, 2026, 08:34 PM UTC
We are continuing to work on a fix for this issue.
- identified Jul 21, 2026, 08:52 PM UTC
Actors are now fully operational, and the system is processing all the runs in time.
- monitoring Jul 21, 2026, 09:28 PM UTC
All systems are operational. We expect the database to fully recover in 4 hours (1 am UTC). We are monitoring the platform's performance. We apologize for any inconvenience this might have caused.
- resolved Jul 22, 2026, 02:38 AM UTC
The database is fully recovered, and all systems are operational. We apologize for any inconvenience this might have caused. We are currently implementing new measures to ensure this won't happen again.
Minor July 21, 2026 High number of Actor run migrations 5h 1m Actors
Started Jul 21, 2026, 06:52 AM UTC· resolved Jul 21, 2026, 11:53 AM UTC
- 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.
Minor July 17, 2026 Degraded SERP performance 6h 3m SERP
Started Jul 17, 2026, 02:04 PM UTC· resolved Jul 17, 2026, 08:08 PM UTC
- 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.
Minor June 4, 2026 Degraded performance of webhooks 1h 59m Webhooks
Started Jun 04, 2026, 03:07 PM UTC· resolved Jun 04, 2026, 05:07 PM UTC
- 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.
Minor May 15, 2026 Degraded performance of API, Console, and Proxy 17h 39m Datacenter, Console (console.apify.com), Residential, API (api.apify.com) and 1 more
Started May 15, 2026, 11:48 AM UTC· resolved May 16, 2026, 05:28 AM UTC
- 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.
Critical May 14, 2026 Proxy degradation 5m
Started May 14, 2026, 07:20 AM UTC· resolved May 14, 2026, 07:25 AM UTC
- resolved May 14, 2026, 07:20 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.
Minor May 6, 2026 MCP: Failing OAuth sing-in from clients using CIMD with loopback redirects 12h 18m MCP server (mcp.apify.com)
Started May 06, 2026, 08:08 PM UTC· resolved May 07, 2026, 08:27 AM UTC
- 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.
Critical May 5, 2026 Outage of Key-value store 44m Console (console.apify.com)
Started May 05, 2026, 01:50 PM UTC· resolved May 05, 2026, 02:34 PM UTC
- 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.
Minor May 1, 2026 Degraded Console UI and API performance 33m Console (console.apify.com), API (api.apify.com)
Started May 01, 2026, 11:23 AM UTC· resolved May 01, 2026, 11:57 AM UTC
- 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.
Major April 29, 2026 Outage of API and Actors 2h 38m Console (console.apify.com), API (api.apify.com), Actors
Started Apr 29, 2026, 12:35 PM UTC· resolved Apr 29, 2026, 03:13 PM UTC
- 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.
Major April 8, 2026 Apify API Degraded Performance 23h 14m Console (console.apify.com), API (api.apify.com), Actors
Started Apr 08, 2026, 10:01 AM UTC· resolved Apr 09, 2026, 09:15 AM UTC
- 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.
Notice March 11, 2026 Security Incident Notification – March 6, 2026 20h 46m General
Started Mar 11, 2026, 12:48 PM UTC· resolved Mar 12, 2026, 09:34 AM UTC
- monitoring Mar 11, 2026, 12:48 PM UTC
We are informing you about a security incident that occurred on March 6, 2026. Based on our investigation to date, there is no indication that any customer data was affected or compromised. However, we want to share the information we have with you as part of our ongoing commitment to transparency. What happened At approximately 21:52 UTC on March 6, 2026, we detected that the GitHub account of one of our employees had been compromised as part of a broader, known malware campaign. The attacker used this access to inject malicious code into multiple branches across our GitHub repositories via force-pushed commits. Thanks to branch protection rules in place on our repositories, no changes were merged into any default or protected branches. How we responded Upon detection, we immediately suspended the affected account and blocked all associated access across our internal systems. Our engineering team then identified all affected branches and reverted every malicious commit. Full cleanup was completed by approximately 00:32 UTC on March 7, 2026. What we have investigated We have since conducted a thorough review of our GitHub audit logs, AWS CloudTrail logs, Google Workspace logs, and all other important resources. All activity reviewed was consistent with expected patterns — no unauthorized access, no suspicious logins, and no signs of data exfiltration were identified beyond the GitHub repository commits, which have been fully reverted. Despite no signs of malicious access, we also completed the rotation of secrets and the scan of all working machines used by Apify employees. Impact on your data Based on our investigation to date, there is no evidence that any customer data was accessed or affected by this incident. The attack was limited to source code repository branches, all of which were protected and have been restored. We take the security of your data seriously and will continue analyzing the impact of the issue and monitoring for any further indicators of compromise. We will provide an update if our ongoing investigation reveals any new findings. Please don't hesitate to reach out to [email protected] if you have any questions. Sincerely, The Apify security team
- resolved Mar 12, 2026, 09:34 AM UTC
This incident has been resolved.
Minor March 6, 2026 Degraded Datacenter Proxy Performance 1h 37m Datacenter
Started Mar 06, 2026, 05:27 PM UTC· resolved Mar 06, 2026, 07:05 PM UTC
- 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.
Minor January 27, 2026 Degraded residential proxy performance 5h 27m Residential
Started Jan 27, 2026, 04:10 AM UTC· resolved Jan 27, 2026, 09:37 AM UTC
- 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.
Critical January 21, 2026 Apify Console temporarily unvailable 2m Console (console.apify.com)
Started Jan 21, 2026, 03:17 PM UTC· resolved Jan 21, 2026, 03:19 PM UTC
- 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.
Minor January 12, 2026 apify.com/store disrupted 36m Web (apify.com)
Started Jan 12, 2026, 08:22 AM UTC· resolved Jan 12, 2026, 08:58 AM UTC
- 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.
Notice January 9, 2026 Customer support chat unavailable 46m Web (apify.com), Console (console.apify.com)
Started Jan 09, 2026, 08:26 PM UTC· resolved Jan 09, 2026, 09:13 PM UTC
- 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.
Major December 31, 2025 Degraded perfromance of residential proxy network 18m Residential
Started Dec 31, 2025, 10:31 AM UTC· resolved Dec 31, 2025, 10:50 AM UTC
- 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.
Minor December 11, 2025 Creating new Actors from Actor templates in UI is unavailable 2h 29m Console (console.apify.com)
Started Dec 11, 2025, 02:56 PM UTC· resolved Dec 11, 2025, 05:26 PM UTC
- 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.