Nebius

Affected: Identity and Access Management

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-18 14:07 UTC

   The console and IAM were unavailable for approximately 10 minutes. The incident has been mitigated, and service availability has been restored.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: API, API, API, API, API, API, API, API, API

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-16 13:02 UTC

   Some users may experience login failures when authenticating with the Nebius CLI via `auth.eu.nebius.com`.

2. resolved 2026-10-16 13:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 05:34 UTC

   We are currently investigating this issue.

2. investigating 2026-10-15 09:32 UTC

   We have identified the root cause and taken the necessary corrective actions to address the issue. We are monitoring the service to confirm recovery.

3. monitoring 2026-10-15 13:13 UTC

   We have taken corrective actions to stabilize the affected infrastructure and are working to address the root cause. Recovery is still in progress, and we are closely monitoring service health. We will confirm mitigation once recovery and stability checks are complete.

4. resolved 2026-10-15 16:12 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Network Block Storage, API, Management Console

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 20:41 UTC

   We are currently experiencing network connectivity issues between the eu-south1 region and other Nebius regions. Cross-region network traffic may be disrupted or experience degraded performance. Our team is investigating the issue and working to restore normal connectivity. We...

2. identified 2026-10-14 22:07 UTC

   We have identified the root cause of the connectivity issues and are preparing a fix. Currently, disk snapshot creation in NBS may be affected. Additionally, Nebius Console and API may experience higher latency than usual. We will provide further updates as we work to resolve...

3. identified 2026-10-14 22:08 UTC

   We have identified the root cause of the connectivity issues and are preparing a fix. Currently, disk snapshot creation in NBS may be affected. Additionally, Nebius Console and API may experience higher latency than usual. We will provide further updates as we work to resolve...

4. resolved 2026-10-15 05:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-10-14 09:54 UTC

   We have identified the cause of the InfiniBand connectivity issues. Our on-site team is working to resolve it. We will provide an update as soon as we have more information.

2. resolved 2026-10-14 10:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Monitoring

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-08 08:30 UTC

   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.

2. monitoring 2026-10-08 08:48 UTC

   This incident has been resolved. We are monitoring current status to verify if everything has been restored.

3. resolved 2026-10-08 08:59 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Hardware, power, cooling or another physical failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 16:37 UTC

   We are currently investigating this issue.

2. resolved 2026-10-08 07:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-03 02:30 UTC

   We are investigating InfiniBand connectivity issues affecting some GPU clusters in Compute Cloud in eu-west2. Distributed training jobs on affected clusters may experience degraded interconnect performance or failures. We will provide an update as soon as we have more...

2. identified 2026-10-03 04:45 UTC

   We have identified the cause of the InfiniBand connectivity issues. Our on-site team is working to resolve it. We will provide an update as soon as we have more information.

3. monitoring 2026-10-03 07:44 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-10-03 08:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 15:31 UTC

   We are investigating an issue affecting Managed Kubernetes node groups in all regions. Preemptible nodes that were in a preempted (stopped) state on October 1 or earlier do not auto-start when capacity becomes available. Manually stopping or starting a node group node does not...

2. identified 2026-10-02 15:50 UTC

   The issue has been identified and a fix has been prepared. The issue has limited impact and does not affect running workloads. To avoid possible disruption of customer production workloads over the weekend, deployment is scheduled for early next week. If you are experiencing any...

3. resolved 2026-10-05 15:54 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Compute Cloud, Compute Cloud, Object Storage

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-02 01:34 UTC

   We are currently investigating this issue.

2. monitoring 2026-10-02 01:58 UTC

   Object Storage was partially unavailable in eu-west1. Moreover, we observed problems around creation of new virtual machines and disks in several regions. Now problems have been fixed and teams are monitoring the situation

3. resolved 2026-10-02 02:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Virtual Private Cloud (Networking)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-23 05:20 UTC

   We are currently investigating this issue.

2. identified 2026-09-23 06:03 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-09-23 08:31 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2026-09-23 08:32 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-09-23 08:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-09-22 09:21 UTC

   Incident is resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Compute Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 16:26 UTC

   We are currently experiencing a partial unavailability of our Compute services, which may affect some of your workloads. Our team is actively investigating the issue and working towards a resolution. We will provide further updates as soon as more information becomes available.

2. resolved 2026-09-17 17:09 UTC

   The root cause was found and this incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Identity and Access Management, Identity and Access Management

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-17 10:46 UTC

   We are investigating an issue with IAM Tenants Status change. Customers may not be able to resume their accounts from the suspended state.

2. monitoring 2026-09-17 11:10 UTC

   Root cause is located and fixed. We keep monitoring the resolution.

3. resolved 2026-09-17 11:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Monitoring

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 16:52 UTC

   We are currently investigating this issue.

2. resolved 2026-09-16 18:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Object Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-16 10:45 UTC

   Users might be experiencing a high rate of 5xx errors on upload requests and elevated latency on read requests.

2. identified 2026-09-16 15:12 UTC

   The team has identified the root cause of the issue and is currently applying a fix. We expect the incident to be fully mitigated within two hours.

3. resolved 2026-09-16 15:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Managed Service for SkyPilot

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-14 15:00 UTC

   We are investigating an issue affecting Managed Service for SkyPilot in eu-north1. Requests to create or update SkyPilot clusters, as well as start and stop requests, are failing with HTTP 503 errors. Instances that are already running are not affected and continue to operate...

2. monitoring 2026-09-15 12:19 UTC

   The error rate has dropped to zero. Requests to create, update, start, and stop SkyPilot clusters in eu-north1 are completing successfully again. We are continuing to investigate the root cause and are monitoring the service closely. Instances that were already running have not...

3. resolved 2026-09-15 15:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-09 12:17 UTC

   In some cases VMs may fail to create or metadata inside may not be available. The team has identified the issue and is working on deploying the fix.

2. monitoring 2026-09-09 12:37 UTC

   The fix has been deployed and the team is looking into the instrumentation for any signs of any remaining abnormal behaviour.

3. resolved 2026-09-09 12:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Managed Service for Kubernetes®, Managed Service for Kubernetes®

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-01 16:11 UTC

   Worker nodes of Managed Service for Kubernetes clusters created after 15:13 CET Sep 1 2026 could experience problems connecting to/from other nodes in the same cluster. The root cause is understood and mitigation is underway.

2. monitoring 2026-09-01 16:24 UTC

   The issue may have caused consequential impact to VPC functionality of VMs that are not Managed Service for Kubernetes worker nodes.

3. monitoring 2026-09-01 16:25 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-09-01 16:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Object Storage, Virtual Private Cloud (Networking), Managed Service for Kubernetes®, Token Factory, Managed Service for MLflow, Managed Service for PostgreSQL®, Managed Service for SkyPilot, Serverless AI

Failure mode: A zone, region or data center became unavailable. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-19 10:43 UTC

   We are currently investigating this issue.

2. identified 2026-08-19 11:18 UTC

   The root cause has been identified as overheating hardware. GPU performance is impacted, and some nodes may be unavailable.

3. identified 2026-08-19 12:20 UTC

   We are still experiencing temperature issues in the us-central1. Team is working on it

4. identified 2026-08-19 12:52 UTC

   The root cause was fixed, and the situation is stabilizing. The services are recovering.

5. identified 2026-08-19 13:49 UTC

   Services are gradually continuing to recover.

6. identified 2026-08-19 15:06 UTC

   Services are still gradually continuing to recover. Some virtual machines are already running, but not all of them.

7. identified 2026-08-19 16:00 UTC

   Services are still gradually continuing to recover. Many of the virtual machines are already running, but not all of them.

8. identified 2026-08-19 17:26 UTC

   Most nodes are operating normally. The Managed Service for Kubernetes® is experiencing a partial outage, and the team is actively working to restore it.

9. identified 2026-08-19 19:13 UTC

   Most nodes are operating normally. The Managed Service for Kubernetes® is still degraded, but the situation is improving.

10. identified 2026-08-19 20:50 UTC

    The Managed Service for Kubernetes is nearly fully restored, though a subset of nodes remains unavailable.

11. identified 2026-08-19 21:59 UTC

    Most critical issues have been resolved and the region is operational, though a subset of nodes remains unavailable.

12. resolved 2026-08-20 08:16 UTC

    This incident has been resolved.

13. postmortem 2026-09-01 09:15 UTC

    [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)

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-08-17 13:00 UTC

   Some newly registered users may have experienced issues logging in to the management console between 13:00 UTC on 17 August 2026 and 14:00 UTC on 18 August 2026.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-15 18:25 UTC

   We are currently investigating this issue.

2. resolved 2026-08-15 21:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Virtual Private Cloud (Networking), Monitoring

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 13:30 UTC

   We are investigating an issue with external VPC connectivity

2. monitoring 2026-08-12 13:37 UTC

   According to our metrics, the situation with VPC has stabilised.

3. resolved 2026-08-12 13:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Compute Cloud

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-05 14:27 UTC

   Due to issue with internal services the creation of new VM and other operations may be affected. We are investigating the issue.

2. investigating 2026-08-05 14:29 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-08-05 14:43 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-08-05 15:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Compute Cloud, Compute Cloud, Compute Cloud, Compute Cloud, Compute Cloud, Network Block Storage, Network Block Storage, Network Block Storage, Network Block Storage, Network Block Storage, Network Block Storage, Object Storage, Object Storage, Object Storage, Object Storage, Object Storage, Object Storage, Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Virtual Private Cloud (Networking), Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Managed Service for Kubernetes®, Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management, Billing, Billing, Billing, Billing, Billing, Billing, API, API, API, API, API, API, Management Console, Management Console, Management Console, Management Console, Management Console, Management Console, Monitoring, Monitoring, Monitoring, Monitoring, Monitoring, Monitoring, Logging, Logging, Logging, Logging, Logging, Logging, Audit Logs, Audit Logs, Audit Logs, Audit Logs, Audit Logs, Audit Logs, Mysterybox, Mysterybox, Mysterybox, Mysterybox, Mysterybox, Mysterybox, Token Factory, Token Factory, Token Factory, Token Factory, Token Factory, Token Factory, Managed Service for MLflow, Managed Service for MLflow, Managed Service for MLflow, Managed Service for MLflow, Managed Service for MLflow, Managed Service for MLflow, Managed Service for PostgreSQL®, Managed Service for PostgreSQL®, Managed Service for PostgreSQL®, Managed Service for PostgreSQL®, Managed Service for PostgreSQL®, Managed Service for PostgreSQL®, Container Registry, Container Registry, Container Registry, Container Registry, Container Registry, Container Registry, Marketplace, Marketplace, Marketplace, Marketplace, Marketplace, Marketplace, Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications, Managed Soperator, Managed Soperator, Managed Soperator, Managed Soperator, Managed Soperator, Managed Soperator, Managed Service for SkyPilot, Managed Service for SkyPilot, Managed Service for SkyPilot, Managed Service for SkyPilot, Managed Service for SkyPilot, Managed Service for SkyPilot, Serverless AI, Serverless AI, Serverless AI, Serverless AI, Serverless AI, Serverless AI

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 18:30 UTC

   We are currently investigating this issue.

2. identified 2026-07-27 19:09 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-27 19:10 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-07-27 20:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-22 15:00 UTC

   The eu-north1 region experienced network issues that may have affected the operation of several services. The issue has been resolved, and all services are operating normally.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-14 22:10 UTC

   We are currently investigating this issue.

2. resolved 2026-07-14 22:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications, Standalone Applications

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-07-03 14:50 UTC

   Managed SkyPilot OIDC Login was unavailable since 2 of July. The problem has been identified and resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Object Storage, Monitoring, Logging, Token Factory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 22:33 UTC

   We are currently experiencing partial unavailability of our Monitoring, Object Storage, Token Factory services. Our team is actively investigating the issue and working towards a resolution. We will provide further updates as soon as more information becomes available.

2. investigating 2026-07-01 23:09 UTC

   We are continuing to investigate this issue.

3. investigating 2026-07-01 23:25 UTC

   We are continuing to investigate this issue.

4. monitoring 2026-07-01 23:57 UTC

   A fix has been implemented and we are monitoring results.

5. resolved 2026-07-02 00:17 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud, Network Block Storage

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-30 13:24 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-06-30 13:27 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-06-30 13:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Object Storage

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-24 14:08 UTC

   We are investigating an outage affecting the Object Storage service in the US-CENTRAL1 region.

2. investigating 2026-06-24 14:39 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-06-24 15:01 UTC

   The Object Storage service in the US-CENTRAL1 region has recovered and is operating normally. We are monitoring to confirm stability. Root cause analysis is ongoing

4. resolved 2026-06-24 15:44 UTC

   The Object Storage service in the US-CENTRAL1 region has been fully restored and is operating normally. The root cause has been identified, and corrective measures are in place.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-16 20:02 UTC

   One InfiniBand switch in the fabric-3 cluster is down.

2. resolved 2026-06-16 20:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Virtual Private Cloud (Networking)

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-15 18:27 UTC

   We have noticed that there have been problems with the connection latency to external addresses in eu-north1.

2. resolved 2026-06-15 18:49 UTC

   Connectivity issues are gone now. Intermittent failure is being investigated in the background with the uplink provider, while the Nebius Netowrking team continues to monitor the link closely.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 20:56 UTC

   We're currently investigating an issue affecting Compute instances startup. Some requests to create or start instances may fail. Already-running instances are not affected. Our engineering team is actively investigating.

2. resolved 2026-06-10 23:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-06-09 10:30 UTC

   Some of public IPs became unreachable.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Object Storage, Monitoring, Logging

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-04 09:46 UTC

   An issue with Internet connectivity in the data center has been detected. Impact: - Logs and metrics from virtual machines are not being delivered. - Object Storage is currently unavailable from internet. - Container registry is currently unavailable from internet. - Additional...

2. monitoring 2026-06-04 10:29 UTC

   The issue has been resolved, and affected services have recovered. The situation continues to be monitored to ensure service stability.

3. resolved 2026-06-04 11:14 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Virtual Private Cloud (Networking)

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-02 10:53 UTC

   We are investigating an issue in eu-north1 affecting Virtual Private Cloud (Networking). New public IPv4 addresses cannot currently be allocated to workloads. Customers may be unable to assign a public IP when creating or modifying resources — for example, attaching a public IP...

2. identified 2026-06-02 11:52 UTC

   We have identified the cause: the pool of available public IPv4 addresses in eu-north1 is currently exhausted, which is why new public IPv4 addresses cannot be allocated to workloads. We are reclaiming and reallocating addresses to restore allocation capacity. Workloads that...

3. monitoring 2026-06-02 12:36 UTC

   Public IPv4 address capacity has been restored in eu-north1, and new public IPv4 addresses can be allocated to workloads again. We are monitoring the service to confirm full recovery before resolving this incident.

4. resolved 2026-06-03 11:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2026-05-29 21:22 UTC

   Several servers were rebooted.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-05-19 13:45 UTC

   The issue has been identified and a fix is being implemented.

2. monitoring 2026-05-19 14:40 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-19 15:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Compute Cloud

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-13 18:45 UTC

   We are investigating reduced InfiniBand fabric performance affecting GPU workloads in the uk-south1 region. Customers may observe lower throughput and slower distributed training jobs.

2. resolved 2026-05-13 21:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Management Console, Management Console, Management Console, Management Console, Management Console, Management Console

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-07 21:03 UTC

   Nebius console is unavailable

2. investigating 2026-05-07 21:26 UTC

   We are continuing to investigate this issue.

3. resolved 2026-05-07 21:28 UTC

   Issue resolved 21:10.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Managed Service for Kubernetes®

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-06 12:39 UTC

   Managed Kubernetes operations can take longer than expected, leading to delays or timeouts. Deletion operations are particularly impacted. The team is currently investigating the issue.

2. identified 2026-05-06 13:37 UTC

   The issue has been identified and the fix is being implemented

3. monitoring 2026-05-06 15:42 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-05-07 07:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Token Factory

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-29 15:36 UTC

   The following serverless models are unavailable due to external provider downtime. Qwen/Qwen3-235B-A22B-Thinking-2507-fast Qwen/Qwen3-Next-80B-A3B-Thinking-fast Qwen/Qwen3.5-397B-A17B-fast deepseek-ai/DeepSeek-V3.2-fast openai/gpt-oss-120b-fast

2. resolved 2026-04-30 08:05 UTC

   The external provider has restored operations. All models are now available.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Token Factory, Token Factory, Token Factory, Token Factory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-24 09:46 UTC

   We are currently investigating this issue.

2. monitoring 2026-04-24 10:11 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-04-24 10:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-04-20 08:05 UTC

   The issue has been identified and a fix is being implemented.

2. resolved 2026-04-20 08:30 UTC

   Since 8:30 back to normal.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Token Factory, Token Factory, Token Factory, Token Factory, Token Factory, Token Factory

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-20 07:26 UTC

   We are currently investigating this issue.

2. investigating 2026-04-20 10:09 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-04-20 14:00 UTC

   Most of Data Lab functionality is restored. Data filtering functionality is disabled until future updates.

4. resolved 2026-04-21 09:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Token Factory

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 08:50 UTC

   Users may experience issues when working with the following serverless models in the us-central1 region: - Qwen/Qwen3.5-397B-A17B - MiniMaxAI/MiniMax-M2.5 We are currently investigating the issue and will provide updates as more information becomes available.

2. investigating 2026-04-15 09:47 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-04-15 09:59 UTC

   Impact is mitigated and we are monitoring the situation

4. resolved 2026-04-15 10:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-10 02:00 UTC

   During the night we experienced issues with storage service. While writing for data was not affected (just delayed), but reading logs, accessing metrics and audit trails in console was not possible while the incident was in active stage.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Token Factory

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-07 11:50 UTC

   We are noticing issues with some customers viewing metrics for Dedicated Endpoints in Token Factory. We are currently investigating this issue.

2. monitoring 2026-04-07 12:23 UTC

   The problem was fixed, and we are monitoring the results.

3. resolved 2026-04-07 13:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.

Affected: Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management, Identity and Access Management

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-01 13:58 UTC

   We are currently investigating this issue.

2. identified 2026-04-01 14:31 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-01 14:42 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-04-01 14:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Nebius's status page.