---
id: "INC-apify-4k6n5swkwx5h"
page: "https://infrastack.ai/live/INC-apify-4k6n5swkwx5h"
kind: "incident"
aliases: []
title: "Apify: Major systems outage"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Apify", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["apify", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2025-02-22T22:12:18+00:00"
first_seen_at: "2026-11-12T15:06:32+00:00"
updated_at: "2026-11-12T15:07:42+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/mlqbfmm8klx1", "first_seen_at": "2026-11-12T15:06:32+00:00"}]
exploit_sources: []
---

# Apify: Major systems outage

Link for people: https://infrastack.ai/live/INC-apify-4k6n5swkwx5h (this .md is for agents)

## Affected

- vendor:Apify affected range not listed fixed no fixed version listed

## Timeline

- 2026-11-11T19:46:21+00:00 confirmed by Apify (statuspage) https://stspg.io/7sp049kjvxqb "On 9 and 10 November 2026, an unauthorized third party gained access to parts of Apify’s internal systems."
- 2026-11-11T19:46:21+00:00 confirmed by Apify (statuspage) https://stspg.io/7sp049kjvxqb "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."
- 2026-11-12T15:06:32+00:00 statuspage https://stspg.io/mlqbfmm8klx1

## From the sources

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](mailto:support@apify.com).

Sincerely,  
Apify engineering team

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_