What does this failure look like in production?

In production this failure typically appears during the first tens-to-hundreds of training steps: loss curves become non-monotonic, validation metrics plateau above the baseline, and downstream checkpoints either diverge or fail to improve. Engineers frequently misread it as data drift when the underlying mechanism is primary isp fiber link was physically damaged the day before the outage, shifting all traffic to secondary isp. Validating against the symptom list in this entry is the fastest way to confirm the diagnosis.

Is this a hardware or a software issue?

Infrastructure failures can look like either layer depending on the symptom. The discriminator is the resolution of the symptom to the recommended fix: if applying the steps under "How to fix it" eliminates the symptom, this is a software/configuration class issue regardless of the hardware it surfaced on. Repeat the fix on a fresh node to confirm.

How long does the fix typically take?

Most resolutions from this entry take 10 to 30 minutes of engineer time once the diagnosis is confirmed. Long fixes come from skipping the diagnosis step and chasing apparent symptoms (validation drift, memory growth, slow throughput) instead of the actual root cause listed above. Apply the fix in a small experiment first, then roll it forward.

Does this affect inference or only training?

Primarily this is a infrastructure failure observed during training, but the same misconfiguration can leak into downstream evaluation and serving. Treat the prevention checklist as a guardrail: any pipeline that touches a trained checkpoint should re-validate the failure mode before promoting the model.

What's the cheapest way to confirm this is the problem?

Cheapest signal: reproduce the symptom on a 1-GPU toy run with the same configuration. If the toy run exhibits the same behavior, the cause is the configuration rather than the cluster. If only the multi-GPU run is affected, the failure is a distributed interaction, so GPU cloud regions relying on 2 or fewer ISPs for network transit is the most likely layer to inspect.

Can the Denpex platform detect this automatically?

Yes. Denpex correlates the symptoms in this entry against your training logs in real time and surfaces the failure taxonomy, root cause, and exact remediation command on the console. Three full diagnoses are included free during signup, and the encyclopedia entry you are reading is generated from the same signal library that powers the platform.

What related failures should I check next?

Closely related failures cluster around #lambda, #bgp, #isp. After applying this fix, validate against the related entries below to confirm no overlapping cause is masking as this one. Engineers routinely discover that the dominant failure mode is actually a second, sibling failure compounded on top.

Will this recur after the fix?

Applied once with the prevention checklist, this failure does not recur under normal operation. The recurring variant most engineers encounter is the re-emergence of the same symptom on a different model or stack after lambda is upgraded. Pin compatible versions and rerun the prevention smoke test on every dependency change.

Is there a fingerprint I can monitor?

Yes. Users cannot SSH or connect to instances in the affected region is the highest-signal fingerprint. Wire a metric or alert on that signal (or its absence after the fix) so you can detect the recurrence automatically. The Denpex platform encodes this exact fingerprint and surfaces it directly in the dashboard.

What is the official documentation that covers this?

Reference documentation is listed in the References section at the bottom of this entry. The most authoritative URLs are the upstream framework docs and the issue trackers cited; the Denpex entry synthesizes both into the executive, engineer, and on-call perspectives so each audience can act without reading every linked source.

Does this entry include working code?

Yes. The "Code Examples" section contains copy-paste-ready snippets that target the most common stacks (PyTorch, Hugging Face Trainer, DeepSpeed, Megatron-LM, vLLM/Transformers). Each snippet is annotated with why it works so you can adapt the pattern to your own framework without losing fidelity.

Dual ISP BGP Route Withdrawal Causing Complete GPU Cloud Region Outage

Q: How does this scale from 1 GPU to 1000 GPUs?

At single-GPU scale the symptom usually looks like slow convergence or a single anomalous loss value. At 64+ GPU scale, distributed interactions amplify primary isp fiber link was physically damaged the day before the outage, shifting all traffic to secondary isp through collectives, and the failure can manifest as a full job abort. Always reproduce the fix at the smallest cluster configuration that still exhibits the symptom before promoting to production scale.

Lambda Labs' us-south-3 region experienced a complete network outage when both redundant ISPs simultaneously stopped advertising BGP routes. The primary fiber link was damaged the prior day, shifting traffic to the secondary ISP. When the secondary ISP also stopped advertising routes, all network connectivity to the region was lost, making cloud instances inaccessible for an extended period.

Quick answer

Lambda Labs' us-south-3 region experienced a complete network outage when both redundant ISPs simultaneously stopped advertising BGP routes.

Root cause: Primary ISP fiber link was physically damaged the day before the outage, shifting all traffic to secondary ISP. Secondary ISP suffered a separate physical fiber cut or routing configuration issue that stopped BGP advertisement. Complete loss of route advertisement left the region's IP space unreachable from any upstream.
Recommended fix: Engage both ISPs simultaneously to diagnose physical layer issues: one team per provider
How Denpex helps: Denpex investigates Dual ISP BGP Route Withdrawal Causing Complete GPU Cloud Region Outage using the evidence you provide or your connected workload collects. Earlier rank, host or application evidence is needed to distinguish an initiating failure from a downstream report.

Infrastructure#lambda#bgp#isp#network-outage#region-failure#redundancy

What this failure is

Dual ISP BGP Route Withdrawal Causing Complete GPU Cloud Region Outage is a Infrastructure failure seen during ML training runs. Lambda Labs' us-south-3 region experienced a complete network outage when both redundant ISPs simultaneously stopped advertising BGP routes. The primary fiber link was damaged the prior day, shifting traffic to the secondary ISP. When the secondary ISP also stopped advertising routes, all network connectivity to the region was lost, making cloud instances inaccessible for an extended period. Common tags: Lambda, Bgp, Isp, Network Outage.

Live diagnosis, no signup

Is this what broke your run? Paste your log.

You're reading about Dual ISP BGP Route Withdrawal Causing Complete GPU Cloud Region Outage. Paste your own traceback and relevant evidence for an investigation of your workload, with a next action or a specific missing fact. A reference entry does not establish your cause. No account or card for the free diagnosis. Review data handling before submitting sensitive logs.

Before uploading, review cloud data handling and local options.

training_logs.txt

No log to hand? Try one:

Upload or drop a plain-text log

Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.

3 free diagnoses/day

Why it happens (the mechanism)

Primary ISP fiber link was physically damaged the day before the outage, shifting all traffic to secondary ISP. Secondary ISP suffered a separate physical fiber cut or routing configuration issue that stopped BGP advertisement. Complete loss of route advertisement left the region's IP space unreachable from any upstream. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.

What you'll observe

All cloud instances in a region become unreachable from the public internet
Both redundant network providers have simultaneously lost connectivity
No BGP routes advertised for the region's IP space

Common symptoms and what they mean

Symptom	Why it happens
Users cannot SSH or connect to instances in the affected region	Primary ISP fiber link was physically damaged the day before the outage, shifting all traffic to secondary ISP
BGP looking glass shows no routes advertised for the region prefix	Secondary ISP suffered a separate physical fiber cut or routing configuration issue that stopped BGP advertisement
Network connectivity to the data center is completely severed	Complete loss of route advertisement left the region's IP space unreachable from any upstream

Which systems are affected

GPU cloud regions relying on 2 or fewer ISPs for network transit
Regions without redundant fiber path diversity (different physical routes)
Infrastructure without BGP session monitoring and alerting

How to confirm this is the problem

Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.

✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
✓Verified signal present: Users cannot SSH or connect to instances in the affected region
✓Verified signal present: BGP looking glass shows no routes advertised for the region prefix
✓Verified signal present: Network connectivity to the data center is completely severed
✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.

Root cause

Primary ISP fiber link was physically damaged the day before the outage, shifting all traffic to secondary ISP
Secondary ISP suffered a separate physical fiber cut or routing configuration issue that stopped BGP advertisement
Complete loss of route advertisement left the region's IP space unreachable from any upstream

The fix and how to prevent it

The fix and the prevention pattern

The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.

No credit card. Daily allowance follows verified trust tier. Instant access.

Diagnose this failure in VS Code

Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.

Install the free VS Code extension