Rewindex

ChangesNebiusRegion us-central1 partial degradation

Nebius: Major incident: Region us-central1 partial degradation

Major incidentmajor (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Nebius removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Region us-central1 partial degradation
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2026-08-19 10:43 UTC
AddedResolved time#5
Before: not present
After: 2026-08-20 08:16 UTC
AddedAffected components#6
Before: not present
After: Compute Cloud, Managed Service for Kubernetes®, Managed Service for MLflow, Managed Service for PostgreSQL®, Managed Service for SkyPilot, Object Storage, Serverless AI, Token Factory, US-CENTRAL1 - Compute Cloud, US-CENTRAL1 - Managed Service for Kubernetes®, US-CENTRAL1 - Managed Service for MLflow, US-CENTRAL1 - Managed Service for PostgreSQL®, US-CENTRAL1 - Managed Service for SkyPilot, US-CENTRAL1 - Object Storage, US-CENTRAL1 - Serverless AI, US-CENTRAL1 - Token Factory, US-CENTRAL1 - Virtual Private Cloud (Networking), Virtual Private Cloud (Networking)
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdateidentified#8
Before: not present
After: The root cause has been identified as overheating hardware. GPU performance is impacted, and some nodes may be unavailable.
AddedUpdateidentified#9
Before: not present
After: We are still experiencing temperature issues in the us-central1. Team is working on it
AddedUpdateidentified#10
Before: not present
After: The root cause was fixed, and the situation is stabilizing. The services are recovering.
AddedUpdateidentified#11
Before: not present
After: Services are gradually continuing to recover.
AddedUpdateidentified#12
Before: not present
After: Services are still gradually continuing to recover. Some virtual machines are already running, but not all of them.
AddedUpdateidentified#13
Before: not present
After: Services are still gradually continuing to recover. Many of the virtual machines are already running, but not all of them.
AddedUpdateidentified#14
Before: not present
After: Most nodes are operating normally. The Managed Service for Kubernetes® is experiencing a partial outage, and the team is actively working to restore it.
AddedUpdateidentified#15
Before: not present
After: Most nodes are operating normally. The Managed Service for Kubernetes® is still degraded, but the situation is improving.
AddedUpdateidentified#16
Before: not present
After: The Managed Service for Kubernetes is nearly fully restored, though a subset of nodes remains unavailable.
AddedUpdateidentified#17
Before: not present
After: Most critical issues have been resolved and the region is operational, though a subset of nodes remains unavailable.
AddedUpdateresolved#18
Before: not present
After: This incident has been resolved.
AddedUpdatepostmortem#19
Before: not present
After: [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)

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

Wednesday, August 19

1 incident change

All Nebius changesNebius profileMarkdownJSON