For nebius ai cloud infrastructure and distributed training engineers
Isolate InfiniBand fabric drops and Soperator node faults on Nebius.
Separate Kubernetes/Slurm Soperator job scheduling events, InfiniBand rail mismatches, and initiating Xid faults before restarting multi-node runs.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a Nebius multi-node InfiniBand collective timeout
Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.
Before uploading, review cloud data handling and local options.
Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.
Try Denpex for 30 days. FREE.
No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.
Start your free 30-day Team evaluation
Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.
What a useful evaluation should establish
Preserve clean hardware and RDMA evidence for Nebius support escalation instead of blindly rerunning multi-node training across the same degraded rail.
Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.
Inside Denpex
See the evidence, not just the claim
Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.
Follow the failure through the cascade

Prepare the hardware escalation

Ask for the evidence that is missing

Keep the investigation in the editor

Nebius - Observed Runtime Evidence
Incident pattern summary
An 8-node H100/B200 training job running on Nebius Kubernetes or Soperator stalls in NCCL AllReduce. Denpex separates socket fallback and RDMA link-flap signatures from healthy ranks timing out downstream.
nebius-h100-03:204:204 [0] NCCL INFO NET/IB : Using [0]mlx5_0:1/IB [1]mlx5_1:1/IB
nebius-h100-03:204:312 [0] NCCL WARN NET/IB : Got async event : port error on mlx5_1
[E ProcessGroupNCCL.cpp:915] [Rank 14] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=842, OpType=ALLREDUCE)Recommended verification flags
Set these environment flags in your training container or launch script to capture high-resolution collective logs:
NCCL_DEBUG=INFONCCL_IB_HCA=mlx5TORCH_NCCL_ASYNC_ERROR_HANDLING=1CUDA_LAUNCH_BLOCKING=1Diagnostic Scope Boundary
Denpex analyzes exported job logs, topology matrices, and kernel outputs. It does not access your private Nebius control plane or InfiniBand subnet manager directly.
Other GPU Cloud Failure Workflows
Compare evidence patterns across multi-node fabrics, Kubernetes pods, and bare-metal environments.