For uk and eu ml engineers on cudo compute h100, h200, and l40s clusters
Untangle virtualized PCIe topology and /dev/shm traps on CUDO Compute.
Verify peer-to-peer memory access flags, shared-memory mounts, and private fabric interfaces before attributing stalls to model code.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a CUDO Compute multi-GPU training crash
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
Distinguish one-line NCCL environment fixes from underlying hypervisor host issues in under two minutes.
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

CUDO Compute (UK & Europe) - Observed Runtime Evidence
Incident pattern summary
A 4x H100 PCIe VM on CUDO Compute UK fails inside initTransportsRank due to host IOMMU P2P blocking or undersized container shared memory.
cudo-lon-01:510:532 [1] NCCL WARN Cuda failure 'peer access is not supported between these two devices'
RuntimeError: DataLoader worker (pid 1842) is killed by signal: Bus error. Possible cause: insufficient shared memory (/dev/shm).Recommended verification flags
Set these environment flags in your training container or launch script to capture high-resolution collective logs:
NCCL_DEBUG=INFONCCL_P2P_DISABLE=1NCCL_SHM_DISABLE=0TORCH_NCCL_ASYNC_ERROR_HANDLING=1Diagnostic Scope Boundary
Denpex evaluates your logs and configuration captures read-only and never modifies hypervisor IOMMU passthrough settings.
Other GPU Cloud Failure Workflows
Compare evidence patterns across multi-node fabrics, Kubernetes pods, and bare-metal environments.