User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 1222 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 06:45 | 0 | 0.0 | 1097 ms | 0 |
| 08:45 | 0 | 0.0 | 982 ms | 0 |
| 11:00 | 0 | 0.0 | 1759 ms | 0 |
| 13:00 | 0 | 0.0 | 1090 ms | 0 |
| 15:00 | 0 | 0.0 | 1082 ms | 0 |
| 17:00 | 0 | 0.0 | 1264 ms | 0 |
| 19:15 | 0 | 0.0 | 902 ms | 0 |
| 21:15 | 0 | 0.0 | 1183 ms | 0 |
| 23:15 | 0 | 0.0 | 1263 ms | 0 |
| 23:45 | 0 | 0.0 | 1136 ms | 0 |
| 01:45 | 0 | 0.0 | 993 ms | 0 |
| 03:30 | 0 | 0.0 | 1222 ms | 0 |
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.
ID-porten - BankID utfører vedlikehold med nedetid 15.11.26 kl. 00:00 til 07:00
BankID utfører vedlikehold 15.11.26 kl. 00:00 til 07:00. Forventet konsekvens: - Ca. 00:00 - 03:00 - Alle BankID-tjenester vil være utilgjengelige - Ca. 03:00 - 07:00 - Det må påregnes ustabilitet i BankID-tjenestene. Dette kan medføre at enkelte autentiserings- og signeringsforsøk ikke kan gjennomføres som normalt.
ELMA - vedlikehold i PEPPOL som kan påvirke SML
Peppol vil utføre vedlikahald i produksjonsmiljøet tirsdag 17 november, klokka 10:00. Oppslag skal fungere normalt i vedlikehaldsvindauget, men oppretting og sletting kan ta litt lenger tid enn vanleg.
MinID - Fornying av tls-sertifikat for minid.no, 18.11.2026, 08:00-09:00 CEST (UTC+2)
We will be undergoing scheduled maintenance during this time.
ID-porten og Maskinporten - vedlikehold med kortvarig nedetid - 18.11.2026
Det blir utført vedlikehold i ID-porten og Maskinporten onsdag 18. november kl 16:00 - 16:30 Dette fører til to korte perioder med nedetid (5-10 sek) innenfor 2 minutter i løpet av vedlikeholdsperioden.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
All Digitaliseringsdirektoratet outages · Every recent outage
One report per service every 10 minutes from this network. No account.
Get an email when Digitaliseringsdirektoratet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Digitaliseringsdirektoratet alerts to Slack, Discord or a webhook — free.
Digitaliseringsdirektoratet is listed in our Cloud & developer category and checked at digdir.no. Digitaliseringsdirektoratet skal bidra til en mer effektiv, brukerorientert og samordnet offentlig sektor med økt deltakelse, verdiskapning og innovasjon.
Digitaliseringsdirektoratet publishes an official status page at status.digdir.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 7 days of checks. We logged 1 public incident since monitoring began 7 days ago.
Response time over the last 24 hours: 1114 ms average, 724–1759 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
The most recent public incident we recorded started 2026-11-10 and lasted 2 h 6 min. 1 incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1114 ms on average over the last 24 hours (724–1759 ms).
Yes, at https://status.digdir.no.
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 Digitaliseringsdirektoratet here at once, the problem is on Digitaliseringsdirektoratet'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 Digitaliseringsdirektoratet. 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.