This caused our IP routing network to malfunction. We have identified the cause of the outage to a network system failure following an update in our core IP network during the early morning of Friday July 8th. Rogers ResponseĪt a high level, Rogers starts by confirming that they had identified the cause of the outage. I'll go through what I see as the important questions and perspective as we go through the response. You can read the full letter above, but effectively it's an outline of questions that Rogers has been asked to respond to. And adds the basis for this outreach, including disruptions to business, emergency services, and more. The letter itself basically outlines that the Canadian Radio-television and Telecommunications Commission (CRTC) wants to inquire into the outage that began on July 8th, 2022. Rogers unable to switch customers to Bell, Telus, despite competing carrier offers - Toronto Star.Rogers shares explanation after 'unprecedented' outage - National Post.
How a coding error caused Rogers outage that left millions without service - Globe and Mail.If you're instead interested in a media level analysis, here are some of the media reports i've found. But I still dug through the report to try and find what useful information I could. Unfortunately, the redacted version removes almost all the useful information for other carriers or other industries to learn from this outage. I've been out of the industry for a few years now, but my outdated perspective may be of some use here. I started my career in wireless telecommunications for a competitor to Rogers here in Canada, and wanted to dig through the outage. Last week, the CRTC made public a redacted version of the response Rogers filed with answers to the regulators questions.
0 kommentar(er)
