User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Bronnoysundregistrene 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 → brreg.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 56 min ago. Last stored result reached it in 732 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 09 | 0 | 0.0 | 767 ms | 0 |
| Wed 12 | 0 | 0.0 | 796 ms | 0 |
| Wed 14 | 0 | 0.0 | 669 ms | 0 |
| Wed 16 | 0 | 0.0 | 871 ms | 0 |
| Wed 18 | 0 | 0.0 | 911 ms | 0 |
| Wed 20 | 0 | 0.0 | 714 ms | 0 |
| Wed 22 | 0 | 0.0 | 693 ms | 0 |
| Thu 01 | 0 | 0.0 | 765 ms | 0 |
| Thu 03 | 0 | 0.0 | 757 ms | 0 |
| Thu 05 | 0 | 0.0 | 793 ms | 0 |
| Thu 07 | 0 | 0.0 | 796 ms | 0 |
| Thu 09 | 0 | 0.0 | 877 ms | 0 |
| Thu 11 | 0 | 0.0 | 792 ms | 0 |
| Thu 13 | 0 | 0.0 | 816 ms | 0 |
| Thu 15 | 0 | 0.0 | 911 ms | 0 |
| Thu 17 | 0 | 0.0 | 792 ms | 0 |
| Thu 19 | 0 | 0.0 | 680 ms | 0 |
| Thu 21 | 0 | 0.0 | 866 ms | 0 |
| Thu 23 | 0 | 0.0 | 649 ms | 0 |
| Fri 01 | 0 | 0.0 | 759 ms | 0 |
| Fri 03 | 0 | 0.0 | 743 ms | 0 |
| Fri 06 | 0 | 0.0 | 731 ms | 0 |
| Fri 08 | 0 | 0.0 | 714 ms | 0 |
| Fri 10 | 0 | 0.0 | 685 ms | 0 |
| Fri 11 | 0 | 0.0 | 750 ms | 0 |
| Fri 12 | 0 | 0.0 | 646 ms | 0 |
| Fri 14 | 0 | 0.0 | 618 ms | 0 |
| Fri 16 | 0 | 0.0 | 821 ms | 0 |
| Fri 18 | 0 | 0.0 | 763 ms | 0 |
| Fri 20 | 0 | 0.0 | 762 ms | 0 |
| Fri 22 | 0 | 0.0 | 823 ms | 0 |
| Sat 00 | 0 | 0.0 | 765 ms | 0 |
| Sat 02 | 0 | 0.0 | 797 ms | 0 |
| Sat 04 | 0 | 0.0 | 802 ms | 0 |
| Sat 06 | 0 | 0.0 | 786 ms | 0 |
| Sat 07 | 0 | 0.0 | 931 ms | 0 |
| Sat 09 | 0 | 0.0 | 766 ms | 0 |
| Sat 11 | 0 | 0.0 | 575 ms | 0 |
| Sat 13 | 0 | 0.0 | 772 ms | 0 |
| Sat 16 | 0 | 0.0 | 783 ms | 0 |
| Sat 18 | 0 | 0.0 | 831 ms | 0 |
| Sat 20 | 0 | 0.0 | 870 ms | 0 |
| Sat 23 | 0 | 0.0 | 848 ms | 0 |
| Sun 02 | 0 | 0.0 | 791 ms | 0 |
| Sun 04 | 0 | 0.0 | 735 ms | 0 |
| Sun 06 | 0 | 0.0 | 1237 ms | 0 |
| Sun 08 | 0 | 0.0 | 737 ms | 0 |
| Sun 10 | 0 | 0.0 | 732 ms | 0 |
Reliability
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 10 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Bronnoysundregistrene 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
Having trouble with Bronnoysundregistrene?
One report per service every 10 minutes from this network. No account.
Follow Bronnoysundregistrene
Get an email when Bronnoysundregistrene goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
About Bronnoysundregistrene
We track Bronnoysundregistrene (brreg.no) as part of the Cloud & developer group. På brreg.no kan du registrere og endre opplysninger på bedrift, finne bedriftsinformasjon og kunngjøringer, sjekke heftelser i bil og stoppe telefonsalg
Bronnoysundregistrene publishes an official status page at status.brreg.no; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 10 days of checks. We logged 1 public incident since monitoring began 10 days ago.
Response time over the last 24 hours: 807 ms average, 575–1237 ms range across 13 successful checks.
Questions
Is Bronnoysundregistrene down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Bronnoysundregistrene last down?
The most recent public incident we recorded started 2026-11-10 and lasted 2 h 5 min. 1 incident since monitoring began 10 days ago.
What is Bronnoysundregistrene's uptime?
From our own checks: 100% over 10 days of checks.
How fast does Bronnoysundregistrene respond?
807 ms on average over the last 24 hours (575–1237 ms).
Does Bronnoysundregistrene have an official status page?
Yes, at https://status.brreg.no.
Bronnoysundregistrene 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 Bronnoysundregistrene here at once, the problem is on Bronnoysundregistrene'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 Bronnoysundregistrene. 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.