Is Apify down?
Last checked just nowNo incidents right now.
Apify is operational right now. Last checked just now; the most recent incident resolved 35d ago.
Real-time Apify status, recent outages, and incident history: pulled directly from Apify's official status page at status.apify.com every 5 minutes. Pingoru tracks 26 Apify services and has captured 5 incidents in the last 90 days (99.57% uptime). Get email, Slack, Discord, or webhook alerts the moment Apify reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days-
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.
Latest: Some Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved.
-
- 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.
Latest: This incident has been resolved.
-
- 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.
Latest: This incident has been resolved.
-
- 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.
Latest: This incident has been resolved.
-
- SERP
Timeline · 4 updates
- 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.
Latest: The Google SERP Proxy is stabilized, and we continue to monitor its performance.
-
Incident record
Since April 2026 · Statuspage by Atlassian · 26 components checked every 5 minutesThe longest incident in the last year, Degraded performance of Google SERP Proxy on August 3, 2026, ran for 38 hours.
Most affected components, last 12 months
- Console (console.apify.com)8
- API (api.apify.com)6
- Actors6
- SERP4
- Datacenter3
Latest incidents
- Elevated errors in Actor runs
Some Actor runs were experiencing degraded performance, slower start and finish times, and elevated error rates. The issue is resolved.
- Degraded Actor performance
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…
- Degraded performance of SHADER proxy group
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…
- Elevated errors in Actor runs ResolvedStarted Sep 22, 2026, 02:30 PM UTC · Resolved Sep 22, 2026, 02:30 PM UTC · –
- Degraded Actor performance ResolvedStarted Aug 20, 2026, 02:05 PM UTC · Resolved Aug 20, 2026, 04:14 PM UTC · 2h 8m
- Started Aug 13, 2026, 03:38 PM UTC · Resolved Aug 14, 2026, 02:05 PM UTC · 22h 26m
- Started Aug 07, 2026, 09:00 PM UTC · Resolved Aug 08, 2026, 06:59 PM UTC · 21h 59m
- Started Aug 03, 2026, 11:56 PM UTC · Resolved Aug 05, 2026, 01:30 PM UTC · 1d 13h