3rd Yandex Cloud Data Center Was Hit
- ID
- 34162
- Status
- summarized
- Published
- 11 Oct 2026, 3:34 PM
- Fetched
- 11 Oct 2026, 8:19 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://status.yandex.cloud/en/incidents/2136
- Source URL
- https://hnrss.org/best
Summary
- Score
- 4.5
- Created
- 11 Oct 2026, 8:19 PM
- Tags
- Audience
- developerssaas_foundersai_ml_learners
What happened
Yandex Cloud's status page reports availability zone outages across All Russia and Kazakhstan, listing dozens of services unavailable—including Compute Cloud, VPC, Object Storage, IAM, Managed Kubernetes, managed PostgreSQL/MySQL/ClickHouse/Kafka, Cloud Functions, and YandexGPT API. An Oct 11 update says Console and API are available, Compute is partially available, S3 is read/write with possible slowdown, Kafka has difficulties, and Kubernetes has issues; quota increases are suspended and support may be delayed. The next update is scheduled for Oct 11 at 18:00 Moscow time (UTC+3); the status text provided does not state a cause or confirm the title's '3rd data center hit' claim.
Why it matters
If you run workloads on Yandex Cloud in those regions, you need a fallback for Compute, Kubernetes, Kafka, managed databases, and YandexGPT API, and you cannot rely on quota increases to scale out during recovery. For everyone else, direct impact is limited; the practical check is whether your own provider's status page distinguishes control-plane/API availability from partial compute and managed-service availability, because this incident shows they can diverge.
Discussion angle
When a provider says the console and API are up but Compute is only partially available and quota increases are suspended, what does your failover runbook actually do—and would you trust a single-region managed database during that window?