Region us-central1 partial degradation
[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)
The latest update from Nebius.
State
Resolved
Started
75 d ago
2026-08-19 10:43 UTC
Lasted
21 h 33 min
until 2026-08-20 08:16 UTC
Worst impact
Partial outage
Timeline
13 updatesInvestigating
35 min 3%
Identified
20 h 58 min 97%
Updates
Times in UTCAs posted by Nebius
[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)
This incident has been resolved.
Most critical issues have been resolved and the region is operational, though a subset of nodes remains unavailable.
The Managed Service for Kubernetes is nearly fully restored, though a subset of nodes remains unavailable.
Most nodes are operating normally. The Managed Service for Kubernetes® is still degraded, but the situation is improving.
Most nodes are operating normally. The Managed Service for Kubernetes® is experiencing a partial outage, and the team is actively working to restore it.
Services are still gradually continuing to recover. Many of the virtual machines are already running, but not all of them.
Services are still gradually continuing to recover. Some virtual machines are already running, but not all of them.
Services are gradually continuing to recover.
The root cause was fixed, and the situation is stabilizing. The services are recovering.
We are still experiencing temperature issues in the us-central1. Team is working on it
The root cause has been identified as overheating hardware. GPU performance is impacted, and some nodes may be unavailable.
We are currently investigating this issue.
Affected components
9Nebius in the last 90 days
Full historyIncidents in 90 days
27
Days with an incident
27
Median duration
1 h 18 min
This incident
17× the median
Other Nebius incidents
All incidentsNebius·Token Factory: some dedicated endpoints partially unavailable
This incident has been resolved.
Nebius·Compute Cloud: disk images and snapshots partial unavailability
The incident has been resolved
Nebius·Token Factory 503 errors in eu-west2
The issue has been resolved.
Nebius·Partial IAM and console unavailability
The console and IAM were unavailable for approximately 10 minutes. The incident has been mitigated, and service availability has been restored.
Nebius·CLI login issues
This incident has been resolved.
Follow Nebius
Your coding agent knows when Nebius is down, and tells you when a failure is theirs, not yours. You can also get Nebius incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "nebius" and tell me if Nebius has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=nebius/feed subscribe https://outages.cc/feed.xml?providers=nebiusFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane