Nebius experienced a major incident on August 19, 2026 affecting Compute Cloud and Object Storage and 1 more component, lasting 21h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 19, 2026, 10:43 AM UTC
We are currently investigating this issue.
- identified Aug 19, 2026, 11:18 AM UTC
The root cause has been identified as overheating hardware. GPU performance is impacted, and some nodes may be unavailable.
- identified Aug 19, 2026, 12:20 PM UTC
We are still experiencing temperature issues in the us-central1. Team is working on it
- identified Aug 19, 2026, 12:52 PM UTC
The root cause was fixed, and the situation is stabilizing. The services are recovering.
- identified Aug 19, 2026, 01:49 PM UTC
Services are gradually continuing to recover.
- identified Aug 19, 2026, 03:06 PM UTC
Services are still gradually continuing to recover. Some virtual machines are already running, but not all of them.
- identified Aug 19, 2026, 04:00 PM UTC
Services are still gradually continuing to recover. Many of the virtual machines are already running, but not all of them.
- identified Aug 19, 2026, 05:26 PM UTC
Most nodes are operating normally. The Managed Service for Kubernetes® is experiencing a partial outage, and the team is actively working to restore it.
- identified Aug 19, 2026, 07:13 PM UTC
Most nodes are operating normally. The Managed Service for Kubernetes® is still degraded, but the situation is improving.
- identified Aug 19, 2026, 08:50 PM UTC
The Managed Service for Kubernetes is nearly fully restored, though a subset of nodes remains unavailable.
- identified Aug 19, 2026, 09:59 PM UTC
Most critical issues have been resolved and the region is operational, though a subset of nodes remains unavailable.
- resolved Aug 20, 2026, 08:16 AM UTC
This incident has been resolved.
- postmortem Sep 01, 2026, 09:15 AM UTC
[https://nebius.com/blog/posts/incident-post-mortem-analysis-us-central1-service-disruption-on-august-19](https://nebius.com/blog/posts/incident-post-mortem-analysis-us-central1-service-disruption-on-august-19)