Apify Outage History
25 incidents recorded over the last 365 days, 25 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Apify Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 22, 2026 | Elevated errors in Actor runsSome Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved. | -36 min | Resolved |
| Aug 20, 2026 | Degraded Actor performanceThis incident has been resolved. | 2h 8m | Resolved |
| Aug 13, 2026 | Degraded performance of SHADER proxy groupThis incident has been resolved. | 22h 26m | Resolved |
| Aug 7, 2026 | Degraded performance of Google SERP ProxyThis incident has been resolved. | 19h 58m | Resolved |
| Aug 3, 2026 | Degraded performance of Google SERP ProxyThe Google SERP Proxy is stabilized, and we continue to monitor its performance. | 37h 33m | Resolved |
| Jul 26, 2026 | Increased error rate on Actor Standby endpointsThe 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. | 1h 4m | Resolved |
| Jul 21, 2026 | Degraded performance of API operations due to slow database operationsThe 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. | 11h 49m | Resolved |
| Jul 21, 2026 | High number of Actor run migrationsAll systems are operational, and we apologize for any inconvenience this might have caused. | 5h 1m | Resolved |
| Jul 17, 2026 | Degraded SERP performanceThe issue has been resolved. Both the response time and success rate have returned to normal levels. | 6h 3m | Resolved |
| Jun 4, 2026 | Degraded performance of webhooksWebhooks are operational, and we apologize for any inconvenience this might have caused. | 1h 59m | Resolved |
| May 15, 2026 | Degraded performance of API, Console, and ProxyThis incident has been resolved. | 17h 39m | Resolved |
| May 14, 2026 | Proxy degradationWe 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… | 0 min | Resolved |
| May 6, 2026 | MCP: Failing OAuth sing-in from clients using CIMD with loopback redirectsWe have implemented a fix for the OAuth flow, and the connections are now working normally. | 12h 18m | Resolved |
| May 5, 2026 | Outage of Key-value storeWe'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… | 44 min | Resolved |
| May 1, 2026 | Degraded Console UI and API performanceThis incident has been resolved. | 33 min | Resolved |
| Apr 29, 2026 | Outage of API and ActorsThis incident has been resolved. | 2h 38m | Resolved |
| Apr 8, 2026 | Apify API Degraded PerformanceAll 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. | 23h 14m | Resolved |
| Mar 11, 2026 | Security Incident Notification – March 6, 2026This incident has been resolved. | 20h 46m | Resolved |
| Mar 6, 2026 | Degraded Datacenter Proxy PerformanceDatacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused. | 1h 37m | Resolved |
| Jan 27, 2026 | Degraded residential proxy performanceThis incident has been resolved. | 5h 27m | Resolved |
| Jan 21, 2026 | Apify Console temporarily unvailableAll 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. | 2 min | Resolved |
| Jan 12, 2026 | apify.com/store disruptedA fix has been implemented, and Apify Store is back to normal operations. | 36 min | Resolved |
| Jan 9, 2026 | Customer support chat unavailableThis incident has been resolved. | 46 min | Resolved |
| Dec 31, 2025 | Degraded perfromance of residential proxy networkThis incident has been resolved. | 18 min | Resolved |
| Dec 11, 2025 | Creating new Actors from Actor templates in UI is unavailableThe issue affecting the creation of new Actors from Actor templates has now been fully resolved. Service is operating normally again. | 2h 29m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Apify incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Apify Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Apify acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Apify outage in this window ran 1d 13h, against a mean recovery of 8h 13m. If you depend on Apify in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.