Rogers Canada 2022 Outage

Network failure.

Overview

On 8 July 2022 a Rogers Communications maintenance window cascaded into a nationwide telecom outage that took out internet, mobile, payment terminals, and 911 across much of Canada for most of the day. The lasting lesson is not the specific BGP misconfiguration; it is what happens when an entire country's payment, emergency, and connectivity layers all sit on a single telecom vendor.

• Maintenance-triggered cascade. A routing-policy change during planned maintenance propagated and broke the production network. Change-window risk is real.
• Single-vendor concentration. Banks, payment processors, and emergency services routed through Rogers exclusively. The blast radius matched the concentration.
• Critical-service impact. Interac payment terminals down, 911 access degraded, hospital systems affected. The dependency chain reached deeper than anyone had modelled.
• Recovery complexity plus regulatory response. Multi-hour restoration because rollback itself depended on the broken control plane; CRTC and government scrutiny followed.

The approach

Three habits make services resilient against single-vendor telecom failure: multi-vendor redundancy on critical paths, named failover for emergency-class functions, and documented supply-chain mapping so the next vendor outage is not the discovery moment.

• Multi-vendor redundancy. Critical paths route through two telecom providers. Cost is real; the alternative is being part of the next national-scale outage.
• Critical-service failover. 911, payment, and healthcare links have named secondary providers and tested switchover. The runbook is rehearsed.
• Documented supply-chain map. Per-service the upstream telecom dependencies. Discovery during the outage is too late.
• Game-day plus shared postmortem. Single-vendor failure is exercised; industry-wide postmortems published so lessons travel.

Why this compounds

The Rogers postmortem reshaped supply-chain thinking across Canadian critical-infrastructure operators. Each architecture review that applies the lesson reduces concentration risk a little more; the cumulative effect across the industry is meaningful.

• Single-vendor risk reduced. Multi-vendor architecture survives the kind of provider outage that would otherwise be terminal.
• Incident response stronger. Tested failover paths cut the outage minutes when a vendor degrades.
• Supply-chain awareness grows. The discipline becomes part of architecture review, not an afterthought.
• Year-one investment, year-two habit. The first multi-vendor design is heavy lift. By the third, vendor concentration is part of the standard review checklist.