User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
Free · No account · No ads
We email you when Digitaliseringsdirektoratet recovers, and if it goes down again. Confirm once by email; unsubscribe anytime.
Prefer a push alert? Follow Digitaliseringsdirektoratet in the free Damn Is It Down app.
On a computer? Add the Chrome extension: when a site will not load, it shows whether it is down for everyone.
Team channel? Send alerts to Slack, Discord or a webhook
Estimated fix: Not enough Digitaliseringsdirektoratet history yet; similar Cloud & developer outages lasted 2 h (median, typically 50 min–7.5 h; 90 outages).
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 12 min ago. Last stored result reached it in 1085 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1201 ms | 0 |
| Nov 7 | 0 | 0.0 | 1195 ms | 0 |
| Nov 7 | 0 | 0.0 | 1220 ms | 0 |
| Nov 7 | 0 | 0.0 | 1188 ms | 0 |
| Nov 8 | 0 | 0.0 | 1055 ms | 0 |
| Nov 8 | 0 | 0.0 | 1083 ms | 0 |
| Nov 8 | 0 | 0.0 | 1234 ms | 0 |
| Nov 8 | 0 | 0.0 | 1063 ms | 0 |
| Nov 9 | 0 | 0.0 | 1020 ms | 0 |
| Nov 9 | 0 | 0.0 | 1148 ms | 0 |
| Nov 9 | 0 | 0.0 | 1084 ms | 0 |
| Nov 9 | 0 | 0.0 | 1122 ms | 0 |
| Nov 10 | 0 | 0.0 | 971 ms | 0 |
| Nov 10 | 0 | 0.0 | 979 ms | 0 |
| Nov 10 | 0 | 0.0 | 1102 ms | 0 |
| Nov 10 | 0 | 0.0 | 1145 ms | 0 |
| Nov 11 | 0 | 0.0 | 1273 ms | 0 |
| Nov 11 | 0 | 0.0 | 1134 ms | 0 |
| Nov 11 | 0 | 0.0 | 1078 ms | 0 |
| Nov 11 | 0 | 0.0 | 1216 ms | 0 |
| Nov 12 | 0 | 0.0 | 1006 ms | 0 |
| Nov 12 | 0 | 0.0 | 1097 ms | 0 |
| Nov 12 | 0 | 0.0 | 1090 ms | 0 |
| Nov 12 | 0 | 0.0 | 1136 ms | 0 |
| Nov 13 | 0 | 0.0 | 993 ms | 0 |
| Nov 13 | 0 | 0.0 | 1108 ms | 0 |
| Nov 13 | 0 | 0.0 | 1118 ms | 0 |
| Nov 13 | 0 | 0.0 | 1088 ms | 0 |
| Nov 14 | 0 | 0.0 | 1071 ms | 0 |
| Nov 14 | 0 | 0.0 | 1263 ms | 0 |
| Nov 14 | 0 | 0.0 | 1217 ms | 0 |
| Nov 14 | 0 | 0.0 | 1147 ms | 0 |
| Nov 15 | 0 | 0.0 | 996 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 9 days of data so far, so the 90-day numbers fill in over time.
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.
Alle tjenesteeiere må oppdatere sine brannmuråpninger på grunn av nye utgående IP-adresser for Altinn Apps i TT02 innen fredag 20. november klokken 14:00
Vi flytter Altinn Apps-klyngene fra Azure-regionen Norway East til Sweden Central. Først flytter vi testmiljøet TT02, deretter produksjon. Flyttingen gir appene deres nye utgående IP-adresser (egress). Dette er adressene som trafikk fra appene til deres egne systemer og API-er kommer fra. Hva dere må gjøre Hvis dere har IP-basert tilgangsstyring mot systemer som appene deres i TT02 kaller, må…
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.
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 9 days of checks. We logged 1 public incident since monitoring began 9 days ago.
Response time over the last 24 hours: 1126 ms average, 848–1494 ms range across 12 successful checks.
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
The most recent public incident we recorded started 2026-11-10 and lasted 2 h 6 min. 1 incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1126 ms on average over the last 24 hours (848–1494 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.