User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Digitaliseringsdirektoratet down?
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
Get a free alert when Digitaliseringsdirektoratet is back
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
What to try while Digitaliseringsdirektoratet is having problems
Estimated fix: Not enough Digitaliseringsdirektoratet history yet; similar Cloud & developer outages lasted 2 h (median, typically 50 min–7.5 h; 90 outages).
- Hold off on deploys and config changes; check which regions or products are affected and retry with backoff.
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 → digdir.no—
Your browser → us—
Our checksReaching it
Official · ReportsMaintenance · 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 848 ms.
Official status
Maintenance
Service Under Maintenance Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Wed 02 | 0 | 0.0 | 1273 ms | 0 |
| Wed 05 | 0 | 0.0 | 1350 ms | 0 |
| Wed 07 | 0 | 0.0 | 997 ms | 0 |
| Wed 09 | 0 | 0.0 | 1229 ms | 0 |
| Wed 11 | 0 | 0.0 | 1117 ms | 0 |
| Wed 13 | 0 | 0.0 | 1038 ms | 0 |
| Wed 15 | 0 | 0.0 | 1118 ms | 0 |
| Wed 18 | 0 | 0.0 | 1216 ms | 0 |
| Wed 20 | 0 | 0.0 | 1337 ms | 0 |
| Wed 22 | 0 | 0.0 | 1063 ms | 0 |
| Thu 00 | 0 | 0.0 | 1337 ms | 0 |
| Thu 02 | 0 | 0.0 | 1006 ms | 0 |
| Thu 04 | 0 | 0.0 | 724 ms | 0 |
| Thu 06 | 0 | 0.0 | 1097 ms | 0 |
| Thu 08 | 0 | 0.0 | 982 ms | 0 |
| Thu 11 | 0 | 0.0 | 1759 ms | 0 |
| Thu 13 | 0 | 0.0 | 1090 ms | 0 |
| Thu 15 | 0 | 0.0 | 1082 ms | 0 |
| Thu 17 | 0 | 0.0 | 1264 ms | 0 |
| Thu 19 | 0 | 0.0 | 902 ms | 0 |
| Thu 21 | 0 | 0.0 | 1183 ms | 0 |
| Thu 23 | 0 | 0.0 | 1200 ms | 0 |
| Fri 01 | 0 | 0.0 | 993 ms | 0 |
| Fri 03 | 0 | 0.0 | 1222 ms | 0 |
| Fri 05 | 0 | 0.0 | 893 ms | 0 |
| Fri 07 | 0 | 0.0 | 1108 ms | 0 |
| Fri 09 | 0 | 0.0 | 1229 ms | 0 |
| Fri 11 | 0 | 0.0 | 1054 ms | 0 |
| Fri 13 | 0 | 0.0 | 1152 ms | 0 |
| Fri 15 | 0 | 0.0 | 1060 ms | 0 |
| Fri 17 | 0 | 0.0 | 1118 ms | 0 |
| Fri 18 | 0 | 0.0 | 918 ms | 0 |
| Fri 20 | 0 | 0.0 | 1271 ms | 0 |
| Fri 22 | 0 | 0.0 | 1088 ms | 0 |
| Fri 23 | 0 | 0.0 | 992 ms | 0 |
| Sat 01 | 0 | 0.0 | 1125 ms | 0 |
| Sat 02 | 0 | 0.0 | 1087 ms | 0 |
| Sat 04 | 0 | 0.0 | 993 ms | 0 |
| Sat 06 | 0 | 0.0 | 1263 ms | 0 |
| Sat 08 | 0 | 0.0 | 1045 ms | 0 |
| Sat 10 | 0 | 0.0 | 1494 ms | 0 |
| Sat 12 | 0 | 0.0 | 1219 ms | 0 |
| Sat 15 | 0 | 0.0 | 1051 ms | 0 |
| Sat 17 | 0 | 0.0 | 1217 ms | 0 |
| Sat 19 | 0 | 0.0 | 1190 ms | 0 |
| Sat 22 | 0 | 0.0 | 1103 ms | 0 |
| Sun 00 | 0 | 0.0 | 996 ms | 0 |
| Sun 02 | 0 | 0.0 | 848 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 9 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Digitaliseringsdirektoratet badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
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.
Announced by Digitaliseringsdirektoratet · sourceMinID - 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.
Announced by Digitaliseringsdirektoratet · sourceID-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.
Announced by Digitaliseringsdirektoratet · sourceAlle 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å…
Announced by Digitaliseringsdirektoratet · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
All Digitaliseringsdirektoratet outages · Every recent outage
Having trouble with Digitaliseringsdirektoratet?
One report per service every 10 minutes from this network. No account.
About Digitaliseringsdirektoratet
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: 1118 ms average, 848–1494 ms range across 12 successful checks.
Questions
Is Digitaliseringsdirektoratet down right now?
The vendor's status page lists scheduled maintenance. Our own checks and user reports have not confirmed a problem. Official status: Service Under Maintenance
When was Digitaliseringsdirektoratet last down?
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.
What is Digitaliseringsdirektoratet's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Digitaliseringsdirektoratet respond?
1118 ms on average over the last 24 hours (848–1494 ms).
Does Digitaliseringsdirektoratet have an official status page?
Yes, at https://status.digdir.no.
Digitaliseringsdirektoratet 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 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.