Bronnoysundregistrene logo

Is Bronnoysundregistrene Down?

SaaSLive status, outages, and incident history

No. Bronnoysundregistrene is up right now.

Every monitored Bronnoysundregistrene system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 1h agoLive, rechecked every 60s
Start monitoring BronnoysundregistreneOfficial Bronnoysundregistrene status page
How we know: the official Bronnoysundregistrene status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Bronnoysundregistrene Component Status

The main Bronnoysundregistrene systems on this page. All 20 are operational right now.

20operational
Bosiden
Operational
Felles mottakssystem
Operational
Grunndatatjenesten WebServices
Operational

17 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Innrapporteringsløsninger » Digital selskapsetablering, Innrapporteringsløsninger » Konkursopplysninger fra tingrettene, Innrapporteringsløsninger » Løsøreregisteret - Maskinporten, Innrapporteringsløsninger » Reelle rettighetshavere, Innrapporteringsløsninger » Samordnet registermelding, Tilgjengeliggjørings API » API - Digital varslingsadresse, Tilgjengeliggjørings API » API - Enhetsregisteret og Foretaksregisteret, Tilgjengeliggjørings API » API - Intet til utlegg/Utleggstrekk, Tilgjengeliggjørings API » API - Konkursvarsel, Tilgjengeliggjørings API » API - roller i Enhets- og Foretaksregisteret, Tilgjengeliggjørings API » API – Ektepaktregisteret, Tilgjengeliggjørings API » API – Frivillighetsregisteret, and 5 more.

Create a free account

Component statuses may change independently during partial outages.

Recent Bronnoysundregistrene Outages & Incidents

Incident history from the official Bronnoysundregistrene status page, including resolution updates.

Uptime history4 days observed
Aug 8100.00% averageAug 11
Problemer med flere av våre tjenesterResolved Aug 3, 2026 · 13h 18mResolved

Problemene som Digdir har opplevd siste døgnet er nå løst, og deres tjenester og da også våre tjenester fungerer nå som normalt. Vi lukker denne saken, men vil fortsatt overvåke våre løsninger i tiden fremover. --- [2026-08-03T21:25:01.522+02:00] (monitoring) Digdir melder om at de fleste tjenestene nå fungerer, men at det fortsatt kan være noe ustabilitet. --- [2026-08-03T19:54:05.882+02:00] (identified) Problemene som tidligere var løst av Digdir har oppstått igjen, og det oppleves ustabilitet knyttet til våre tjenester igjen. Vi oppretter ny varsling her på vår statuspage, og oppdaterer fortløpende når vi har mer informasjon å komme med.

Problemer med flere av våre tjenesterResolved Aug 3, 2026 · 5h 50mResolved

Digdir melder tjenestene er på vei opp igjen, vi ser også at våre tjenester fungerer som de skal. Vi følger uansett litt med utover kvelden, men setter våre tjenester til normal drift. --- [2026-08-03T14:24:44.963+02:00] (monitoring) Digdir melder at trafikken er på vei oppover igjen for de tjenestene som har vært rammet. Trafikken vår er også på vei opp igjen, vi overvåker våre egne tjenester fremover, samt informasjon fra Digdir. --- [2026-08-03T14:01:46.240+02:00] (identified) Digdir melder at fra ca 13:40 så er trafikken på vei opp for tjenestene. Vi oppdaterer mer når vi mottar ny status fra Digdir. --- [2026-08-03T12:23:37.675+02:00] (identified) Digdir har problemer med flere av sine tjenester, som igjen påvirker våre tjenester. Som følge av problemene for ID-porten, Kontakt- og reservasjonsregisteret, Maskinporten, MinID, eFormidling, ELMA, eInnsyn, Ansattporten, så er flere å våre tjenester påvirket.

Problemer med IDportenResolved Jun 20, 2026 · 15h 22mResolved

Problemene med innlogging med IDporten er nå løst. Vi overvåker tjenestene våre en stund fremover. --- [2026-06-20T21:27:18.073+02:00] (identified) Det er fortsatt problemer med innlogging via IDporten. Flere av våre tjenester er fortsatt berørt av problemene. --- [2026-06-20T19:10:24.960+02:00] (identified) We are continuing to work on a fix for this issue. --- [2026-06-20T19:09:10.312+02:00] (identified) Akkurat nå er de innloggende tjenester våre vanskelige å nå på grunn av problemer med ID-porten.

Live Bronnoysundregistrene Outage Reports

Problems reported by engineers using Bronnoysundregistrene. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Bronnoysundregistrene problems reported yet.

Something wrong with Bronnoysundregistrene on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Bronnoysundregistrene

Bronnoysundregistrene exposes 29 monitored components on its status page at status.brreg.no — API - Enhetsregisteret og Foretaksregisteret, Tjenester på brreg.no and Min side among them. Follow Bronnoysundregistrene downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Bronnoysundregistrene uptime at 100.00%. Response times, incident history, and SLA tracking for Bronnoysundregistrene are available on the PulsAPI dashboard.

Bronnoysundregistrene Status FAQ

Is Bronnoysundregistrene down right now?

PulsAPI checks Bronnoysundregistrene every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Bronnoysundregistrene status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Bronnoysundregistrene is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Bronnoysundregistrene recovers.

How do I check Bronnoysundregistrene uptime history?

PulsAPI tracks Bronnoysundregistrene uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Bronnoysundregistrene.

How fast does PulsAPI detect Bronnoysundregistrene outages?

PulsAPI polls the official Bronnoysundregistrene status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Bronnoysundregistrene components?

Yes. PulsAPI monitors 20 individual Bronnoysundregistrene components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Bronnoysundregistrene goes down?

Yes. Create a PulsAPI account and subscribe to Bronnoysundregistrene. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Bronnoysundregistrene status changes.

How do I report an issue with Bronnoysundregistrene to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Bronnoysundregistrene problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Bronnoysundregistrene?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Bronnoysundregistrene alongside up to 9 other services at pulsapi.com/signup.

Track Bronnoysundregistrene with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Bronnoysundregistrene status changes.

Start free trial