Nebius
Nebius is operational
Checked 3 min ago Operational
History
90 days agoToday
Incidents in 90 days
27
Days with an incident
27
Median duration
1 h 18 min
Longest incident
24 h 33 min
Components
198EU-NORTH1
Compute Cloud Operational
90 days ago6 days with an incidentToday
Network Block Storage Operational
90 days agoNo incidentsToday
Object Storage Operational
90 days agoNo incidentsToday
Virtual Private Cloud (Networking) Operational
90 days ago2 days with an incidentToday
Managed Service for Kubernetes® Operational
90 days ago3 days with an incidentToday
Identity and Access Management Operational
90 days ago2 days with an incidentToday
Billing Operational
90 days agoNo incidentsToday
API Operational
90 days ago1 day with an incidentToday
Management Console Operational
90 days agoNo incidentsToday
Monitoring Operational
90 days ago1 day with an incidentToday
Logging Operational
90 days agoNo incidentsToday
Audit Logs Operational
90 days agoNo incidentsToday
Mysterybox Operational
90 days agoNo incidentsToday
Token Factory Operational
90 days agoNo incidentsToday
Managed Service for MLflow Operational
90 days agoNo incidentsToday
Managed Service for PostgreSQL® Operational
90 days agoNo incidentsToday
Container Registry Operational
90 days agoNo incidentsToday
Marketplace Operational
90 days agoNo incidentsToday
Standalone Applications Operational
90 days agoNo incidentsToday
Managed Soperator Operational
90 days agoNo incidentsToday
Managed Service for SkyPilot Operational
90 days ago2 days with an incidentToday
Serverless AI Operational
90 days agoNo incidentsToday
EU-NORTH2
Compute Cloud Operational
90 days ago1 day with an incidentToday
Network Block Storage Operational
90 days agoNo incidentsToday
Oct 16, 2026
Oct 14, 2026
Duration9 h 9 min20:41 to 05:50Connectivity issues between eu-south1 and other Nebius regionsDegraded
This incident has been resolved.status.nebius.com
Duration58 min09:54 to 10:52InfiniBand connectivity issues for GPU clusters in eu-west2Partial outage
This incident has been resolved.status.nebius.com
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.
Prompt
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.
RSS
https://outages.cc/feed.xml?providers=nebiusSlack
/feed subscribe https://outages.cc/feed.xml?providers=nebiusGo from tracking outages to fixing production issues with Polylane.
Try Polylane