CRITICALNO CVE YET

NO KNOWN
EXPLOIT

APIFY · INC-apify-4k6n5swkwx5h · Vendor

resolved

Apify: Major systems outage

NO FIX YET

Not triaged yet. The sources’ own description is below.

first public Feb 22, 2025 · 1 source

Check it with your coding agent

It reads this page and tells you if your code or app is affected.

Claude CodeCodexCursorAdd to your agent

01 · Who is affected

Apify

Who cares apify, ops

02 · How to check

Unknown from the sources.

03 · The fix

Unknown from the sources.

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 12, 2026

How it unfolded

3 events · Nov 11, 2026 → Nov 12, 2026

All 3Disclosed 2

Nov 11, 202619:46 UTCApify On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems.
Nov 11, 202619:46 UTCApify 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.

What the sources say, verbatim

1,432 characters

Saturday outage post-mortem
Date of incident: 2025-02-22

Impact:

Complete downtime of the Apify platform from 22.00 UTC to 23.00 UTC.
No Actors could be started.
Those already running were paused and continued running after the incident was resolved.
There was no data loss, but the workloads were disrupted.

What happened:

Our user base is growing fast, and the number of new signups is increasing exponentially. The exponentially increased load revealed suboptimalities that had not manifested before.
One misconfigured query then caused a peak in memory due to a load of a suboptimal index, which caused the cluster to crash.

What we did:

The cluster size was increased to ensure enough memory until the issue was fixed.
Then, the cluster and all the dependent systems were restarted.

Next steps:

We are already re-architecting our primary database clusters to optimize systems for future growth.
As part of this, we aim to decrease the size of all our clusters to ensure performant restarts in case of a problem.
We are currently optimizing indexing and querying among heavy-load components.
In addition, we identified missing metrics that would indicate similar problems ahead of time.

We sincerely apologize for the disruption and appreciate your patience. If you have any questions, please reach out to support@apify.com.

Sincerely,
Apify engineering team

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

InfraStack checks it against your stack and answers on your report, with the evidence and the fix.

Run the check

Get the next Apify threat the day it hits your stack.

Start free

Post Share

CRITICALNO CVE YET

NO KNOWN
EXPLOIT

APIFY · INC-apify-4k6n5swkwx5h · Vendor

resolved

Apify: Major systems outage

NO FIX YET

Not triaged yet. The sources’ own description is below.

first public Feb 22, 2025 · 1 source

Check it with your coding agent

It reads this page and tells you if your code or app is affected.

Claude CodeCodexCursorAdd to your agent

01 · Who is affected

Apify

Who cares apify, ops

02 · How to check

Unknown from the sources.

03 · The fix

Unknown from the sources.

Exploited: No reports yet
Public exploit: None on GitHub
EPSS: Not scored
Last updated: Nov 12, 2026

How it unfolded

3 events · Nov 11, 2026 → Nov 12, 2026

All 3Disclosed 2

Nov 11, 202619:46 UTCApify On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems.
Nov 11, 202619:46 UTCApify 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.

What the sources say, verbatim

1,432 characters

Saturday outage post-mortem
Date of incident: 2025-02-22

Impact:

Complete downtime of the Apify platform from 22.00 UTC to 23.00 UTC.
No Actors could be started.
Those already running were paused and continued running after the incident was resolved.
There was no data loss, but the workloads were disrupted.

What happened:

Our user base is growing fast, and the number of new signups is increasing exponentially. The exponentially increased load revealed suboptimalities that had not manifested before.
One misconfigured query then caused a peak in memory due to a load of a suboptimal index, which caused the cluster to crash.

What we did:

The cluster size was increased to ensure enough memory until the issue was fixed.
Then, the cluster and all the dependent systems were restarted.

Next steps:

We are already re-architecting our primary database clusters to optimize systems for future growth.
As part of this, we aim to decrease the size of all our clusters to ensure performant restarts in case of a problem.
We are currently optimizing indexing and querying among heavy-load components.
In addition, we identified missing metrics that would indicate similar problems ahead of time.

We sincerely apologize for the disruption and appreciate your patience. If you have any questions, please reach out to support@apify.com.

Sincerely,
Apify engineering team

Are you affected?

Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.

InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.

InfraStack checks it against your stack and answers on your report, with the evidence and the fix.

Run the check

Get the next Apify threat the day it hits your stack.

Start free

Apify: Major systems outage

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next Apify threat the day it hits your stack.

Apify: Major systems outage

01 · Who is affected

02 · How to check

03 · The fix

How it unfolded

What the sources say, verbatim

Read next

Get the next Apify threat the day it hits your stack.

Sources and references