1. Home
  2. Outages
  3. Rogers
  4. 3 Nov 2026

OutageTuesday 3 November 2026Ended 08:44

Rogers outage on 3 November 2026

Problem reports about Rogers rose to outage level at 07:56 Central European time on Tuesday 3 November 2026 and stayed there for 49 min.

They peaked at 164 reports in 15 minutes at 08:08, about 18 times the usual level for that time of day, and 205 reports came in while the outage lasted.

12 other services had an outage spike at the same time.

Is Rogers down right now? 6 outages of Rogers

Started
07:56
Tue 3 Nov, Central European time
At outage level
49 min
Ended 08:44
Busiest 15 minutes
164
reports, at 08:08
Reports during the outage
205
Peak about 18× the usual level
Timeline

Reports from Tue 01:45 to Tue 14:45

One bar per 15 minutes, Central European time. Red bars are the outage; the dashed line is what a usual day sees at that time.

Problem reports about Rogers rose to outage level at 07:56 Central European time on Tuesday 3 November 2026 and stayed there for 49 min. They peaked at 164 reports in 15 minutes at 08:08, about 18 times the usual level for that time of day, and 205 reports came in while the outage lasted. 12 other services had an outage spike at the same time.
Same time

Other services with an outage at the same time

Their reports also reached outage level while Rogers's did. Many services failing together can point to a shared cause, such as a network or cloud provider, but reports alone cannot show it.

More

Rogers: live status and other outages

Check whether Rogers is down right now: the live page shows the last 24 hours and fixes to try. This site keeps a page for each of Rogers's 6 outages since the archive began.

Earlier: 2 Nov 2026 Later: 4 Nov 2026 November 2026 outage report All recent outages

Embed

Put this outage in an article

Copy a frame with the chart and numbers above, or an image of the same card for places that do not allow frames, such as newsletters. Both link back to this page. More for journalists.

Rogers outage on 3 November 2026: problem reports over time

<iframe src="https://isitdownrightnow.app/embed/rogers/2026-11-03/" title="Rogers outage on 3 November 2026" width="100%" height="230" style="border:0;max-width:560px" loading="lazy"></iframe> <p><a href="https://isitdownrightnow.app/services/rogers/outages/2026-11-03/">Rogers outage on 3 November 2026</a> from IsItDownRightNow.app</p>Frame: the chart and numbers, as a small card
<a href="https://isitdownrightnow.app/services/rogers/outages/2026-11-03/"><img src="https://isitdownrightnow.app/share/rogers/2026-11-03.png" alt="Rogers outage on 3 November 2026: problem reports over time" width="600" height="315" loading="lazy"></a>Image: the same card as a picture
[![Rogers outage on 3 November 2026](https://isitdownrightnow.app/share/rogers/2026-11-03.png)](https://isitdownrightnow.app/services/rogers/outages/2026-11-03/)Markdown: the image, for README files and forums

Where these numbers come from

The numbers are problem reports that users sent to a public outage-reporting service, counted in 15-minute windows and kept as this site's live page showed them. A spike counts as an outage when reports are more than twice the usual level and far above the day's average. Reports show that many people had trouble at the same time, not what caused it; the service's own status page is the place for that.