Security incident

What to do

• Check whether you use Apify API (api.apify.com), Actors, General. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.

• Switch to another region or a fallback provider while it is open, if you have one.

  Otherwise back off retries and queue work, so you don't add load while it recovers.

• Watch Apify's own updates; this page re-reads them every minute.

• Subscribe to Apify's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=apify works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Apify 1

1. investigatingNov 11, 2026, 7:46 PM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.