Apify Outage History

Apify is up right now

There were 5 Apify outages since March 6, 2026 totaling 48h 49m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.apify.com

Minor May 1, 2026

Degraded Console UI and API performance

Detected by Pingoru
May 01, 2026, 11:23 AM UTC
Resolved
May 01, 2026, 11:57 AM UTC
Duration
33m
Affected: Console (console.apify.com)API (api.apify.com)
Timeline · 3 updates
  1. 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.

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

  3. resolved May 01, 2026, 11:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 29, 2026

Outage of API and Actors

Detected by Pingoru
Apr 29, 2026, 12:35 PM UTC
Resolved
Apr 29, 2026, 03:13 PM UTC
Duration
2h 38m
Affected: Console (console.apify.com)API (api.apify.com)Actors
Timeline · 4 updates
  1. investigating Apr 29, 2026, 12:35 PM UTC

    We're experiencing degraded performance. We're investigation the cause of the issue

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

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

  4. resolved Apr 29, 2026, 03:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 8, 2026

Apify API Degraded Performance

Detected by Pingoru
Apr 08, 2026, 10:01 AM UTC
Resolved
Apr 09, 2026, 09:15 AM UTC
Duration
23h 14m
Affected: Console (console.apify.com)API (api.apify.com)Actors
Timeline · 6 updates
  1. investigating Apr 08, 2026, 10:01 AM UTC

    We are investigating slow API response times due to underlying database issues.

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

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

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

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

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

Read the full incident report →

Notice March 11, 2026

Security Incident Notification – March 6, 2026

Detected by Pingoru
Mar 11, 2026, 12:48 PM UTC
Resolved
Mar 12, 2026, 09:34 AM UTC
Duration
20h 46m
Affected: General
Timeline · 2 updates
  1. 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

  2. resolved Mar 12, 2026, 09:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Degraded Datacenter Proxy Performance

Detected by Pingoru
Mar 06, 2026, 05:27 PM UTC
Resolved
Mar 06, 2026, 07:05 PM UTC
Duration
1h 37m
Affected: Datacenter
Timeline · 2 updates
  1. 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.

  2. resolved Mar 06, 2026, 07:05 PM UTC

    Datacenter proxy performance has been fully restored. We apologize for any inconvenience this may have caused.

Read the full incident report →

Looking to track Apify downtime and outages?

Pingoru polls Apify's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Apify reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Apify alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Apify for free

5 free monitors · No credit card required