User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
bell.ca · Telecom
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests bell.ca from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 269 ms · 3 min ago.
No status feed
Bell does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 01:15 | 0 | 0.0 | 108 ms | 0 |
| 01:30 | 0 | 0.0 | 265 ms | 0 |
| 01:45 | 0 | 0.0 | 1245 ms | 0 |
| 02:00 | 0 | 0.0 | 302 ms | 0 |
| 02:15 | 0 | 0.0 | 595 ms | 0 |
| 02:30 | 0 | 0.0 | 234 ms | 0 |
| 02:45 | 0 | 0.0 | 269 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Bell yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Bell goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Bell alerts to Slack, Discord or a webhook — free.
Checks are succeeding and user reports are near the baseline.
If Bell is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Bell's side.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.