Public API gateway partially unavailable in US-NORTH1 and US-CENTRAL1
The Public API gateway and the Logging Service do not work fully in US-NORTH1 and US-CENTRAL1. Nebius reports that the issue is under investigation. Read requests to the Logging Service fail in these regions.
State
Investigating
Started
2 h ago
2026-11-02 09:09 UTC
Ongoing for
1 h 41 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 41 min 100%
Updates
Times in UTCAs posted by Nebius
The issues has been located and resolved. Operation for the Public API Gateway in US zone is back to normal.
Read requests to the Logging Service are failing in these regions. We are investigating the issue.
Affected components
6Nebius in the last 90 days
Full historyIncidents in 90 days
28
Days with an incident
28
Median duration
1 h 18 min
This incident
1.3× 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.live/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.live/feed.xml?providers=nebius/feed subscribe https://outages.live/feed.xml?providers=nebiusFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane