User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is BCC down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → bcc.no—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 269 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 121 ms | 0 |
| Mon 15 | 0 | 0.0 | 853 ms | 0 |
| Mon 17 | 0 | 0.0 | 273 ms | 0 |
| Mon 19 | 0 | 0.0 | 628 ms | 0 |
| Mon 21 | 0 | 0.0 | 114 ms | 0 |
| Mon 23 | 0 | 0.0 | 328 ms | 0 |
| Tue 01 | 0 | 0.0 | 394 ms | 0 |
| Tue 04 | 0 | 0.0 | 528 ms | 0 |
| Tue 06 | 0 | 0.0 | 326 ms | 0 |
| Tue 08 | 0 | 0.0 | 128 ms | 0 |
| Tue 10 | 0 | 0.0 | 893 ms | 0 |
| Tue 12 | 0 | 0.0 | 203 ms | 0 |
| Tue 14 | 0 | 0.0 | 384 ms | 0 |
| Tue 16 | 0 | 0.0 | 265 ms | 0 |
| Tue 19 | 0 | 0.0 | 301 ms | 0 |
| Tue 21 | 0 | 0.0 | 105 ms | 0 |
| Tue 23 | 0 | 0.0 | 267 ms | 0 |
| Wed 01 | 0 | 0.0 | 161 ms | 0 |
| Wed 04 | 0 | 0.0 | 646 ms | 0 |
| Wed 06 | 0 | 0.0 | 588 ms | 0 |
| Wed 08 | 0 | 0.0 | 326 ms | 0 |
| Wed 10 | 0 | 0.0 | 137 ms | 0 |
| Wed 13 | 0 | 0.0 | 764 ms | 0 |
| Wed 15 | 0 | 0.0 | 736 ms | 0 |
| Wed 17 | 0 | 0.0 | 294 ms | 0 |
| Wed 19 | 0 | 0.0 | 175 ms | 0 |
| Wed 21 | 0 | 0.0 | 329 ms | 0 |
| Wed 23 | 0 | 0.0 | 1124 ms | 0 |
| Thu 02 | 0 | 0.0 | 175 ms | 0 |
| Thu 04 | 0 | 0.0 | 871 ms | 0 |
| Thu 06 | 0 | 0.0 | 130 ms | 0 |
| Thu 08 | 0 | 0.0 | 1006 ms | 0 |
| Thu 10 | 0 | 0.0 | 214 ms | 0 |
| Thu 12 | 0 | 0.0 | 102 ms | 0 |
| Thu 14 | 0 | 0.0 | 394 ms | 0 |
| Thu 16 | 0 | 0.0 | 767 ms | 0 |
| Thu 18 | 0 | 0.0 | 382 ms | 0 |
| Thu 20 | 0 | 0.0 | 156 ms | 0 |
| Thu 22 | 0 | 0.0 | 370 ms | 0 |
| Fri 00 | 0 | 0.0 | 287 ms | 0 |
| Fri 02 | 0 | 0.0 | 272 ms | 0 |
| Fri 04 | 0 | 0.0 | 522 ms | 0 |
| Fri 06 | 0 | 0.0 | 324 ms | 0 |
| Fri 08 | 0 | 0.0 | 85 ms | 0 |
| Fri 11 | 0 | 0.0 | 84 ms | 0 |
| Fri 12 | 0 | 0.0 | 149 ms | 0 |
| Fri 14 | 0 | 0.0 | 97 ms | 0 |
| Fri 16 | 0 | 0.0 | 269 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live BCC badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for BCC yet. Outages of 10 minutes or more get their own page here.
Having trouble with BCC?
One report per service every 10 minutes from this network. No account.
Follow BCC
Get an email when BCC goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send BCC alerts to Slack, Discord or a webhook — free.
About BCC
We track BCC (bcc.no) as part of the Cloud & developer group. BCC er et kristent trossamfunn med opprinnelse i Norge og internasjonal utbredelse. Les om hvem vi er og hva vi tror på.
BCC publishes an official status page at status.bcc.no; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 271 ms average, 78–965 ms range across 13 successful checks.
Questions
Is BCC down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was BCC last down?
We have not recorded a public BCC incident since monitoring began 7 days ago.
What is BCC's uptime?
From our own checks: 100% over 7 days of checks.
How fast does BCC respond?
271 ms on average over the last 24 hours (78–965 ms).
Does BCC have an official status page?
Yes, at https://status.bcc.no.
BCC not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report BCC here at once, the problem is on BCC's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with BCC. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.