Update - Update: Our investigation is ongoing.

On 9 and 10 November, an unauthorized third party used a compromised credential to obtain a number of account credentials and accessed related Apify accounts. This access path is closed, and we have detected no further activity from the attacker since 11 November.

We are notifying affected users individually. Do not hesitate to reach out to us with questions.

We have:
- As a precaution, revoked some OAuth connections to external integrations. Our investigation has not found that these connections could be used as an attack vector.
- As a precaution, rotated various critical internal secrets.
- We continue with dozens of additional activities, about which we will share information in later updates and a post-mortem.
- We notified the relevant authorities.

For you:
- If you got an email from us, follow its instructions.
- If you build Actors from private GitHub repos, reconnect GitHub: open an Actor built from GitHub → "Change provider" → GitHub → authorize (once per account and per organization).
- If prompted, reconnect your integrations.

Next update within 6 hours, and a postmortem follows the remediation.

Nov 12, 2026 - 12:08 CET
Investigating - On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems. We detected the activity on 11th November at 12:13 UTC, cut off access, and started an investigation that is still ongoing.

We are currently investigating the scope of the incident, including what user data may have been affected. If we determine that your account or data was affected, we will contact you directly.

We have prevented further unauthorized access and added additional monitoring to our systems.

As a precaution, we revoked some OAuth connections to external integrations, including GitHub. Affected users of integrations other than GitHub will be prompted to reconnect via a separate email notification.

If our investigation shows that your tokens were affected, we will rotate them on your behalf and notify you.

Nov 11, 2026 - 20:46 CET

About This Site

See Apify platform status and service incidents. To receive notifications, subscribe to updates or follow https://x.com/apify 

Having issues? Contact us at support@apify.com

Web (apify.com) Operational
Console (console.apify.com) Operational
API (api.apify.com) Partial Outage
Actors Partial Outage
Storage Operational
Dataset Operational
Request queue Operational
Key-value store Operational
Proxy Operational
Datacenter Operational
Residential Operational
SERP Operational
Scheduler Operational
Webhooks Operational
Docs (docs.apify.com) Operational
MCP server (mcp.apify.com) Operational
General 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
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

Nov 12, 2026

Unresolved incident: Security incident.

Nov 11, 2026

Nov 10, 2026

No incidents reported.

Nov 9, 2026

No incidents reported.

Nov 8, 2026

No incidents reported.

Nov 7, 2026

No incidents reported.

Nov 6, 2026

No incidents reported.

Nov 5, 2026

No incidents reported.

Nov 4, 2026

No incidents reported.

Nov 3, 2026

No incidents reported.

Nov 2, 2026

No incidents reported.

Nov 1, 2026

No incidents reported.

Oct 31, 2026

No incidents reported.

Oct 30, 2026

No incidents reported.

Oct 29, 2026

No incidents reported.