Apify Status

Apify

All Systems Operational

About This Site

This is the Apify status page, where you can get updates on how our systems are doing. If there are interruptions to service, we will post a note here. You can also subscribe to get notified via email or sms.

If you are experiencing any issues with Apify, don't hesitate to get in touch with us at support@apify.com, and we'll get back to you as soon as we can. You can also follow us at https://x.com/apify

Web (apify.com) Operational

Console (console.apify.com) Operational

API (api.apify.com) Operational

Actors Operational

Storage Operational

Dataset Operational

Request queue Operational

Key-value store Operational

Proxy Operational

Datacenter Operational

Residential Operational

SERP Operational

Scheduler Operational

Webhooks Operational

External services Operational

AWS EC2 Operational

AWS S3 Operational

AWS SQS Operational

AWS ELB Operational

AWS ElastiCache Operational

AWS ECR Operational

AWS EKS Operational

AWS DynamoDB Operational

Mailgun (API) Operational

Stripe (API) Operational

npm (Package installation) Operational

Docs (docs.apify.com) Operational

MCP server (mcp.apify.com) Operational

General Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Mar 12, 2026

Security Incident Notification – March 6, 2026

Resolved - This incident has been resolved.
Mar 12, 10:34 CET

Monitoring - 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 security@apify.com if you have any questions.

Sincerely,
The Apify security team
Mar 11, 13:48 CET

Mar 11, 2026

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

Degraded Datacenter Proxy Performance

Resolved - Datacenter proxy performance has been fully restored.
We apologize for any inconvenience this may have caused.
Mar 6, 20:05 CET

Identified - We are currently experiencing degraded performance of the datacenter proxy.
The root cause has been identified and we are working on a fix.
Mar 6, 18:27 CET

Mar 5, 2026

No incidents reported.

Mar 4, 2026

No incidents reported.

Mar 3, 2026

No incidents reported.

Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

Feb 26, 2026

No incidents reported.