Metrics unavailable in Management Console for Monitoring in eu-west1
The incident has been resolved.
The latest update from Nebius.
State
Resolved
Started
25 d ago
2026-10-08 08:48 UTC
Lasted
11 min
until 2026-10-08 08:59 UTC
Worst impact
Degraded
Timeline
3 updatesMonitoring
11 min 100%
Updates
Times in UTCAs posted by Nebius
The incident has been resolved.
This incident has been resolved. We are monitoring current status to verify if everything has been restored.
We are investigating an issue with Monitoring in eu-west1. Customers may be unable to view metrics in the Management Console or query them via the Monitoring API. Metrics ingestion is not affected and data continues to be collected. We will update with progress.
Affected components
2Follow 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