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
Estimated fix: Not enough DFO history yet; similar Cloud & developer outages lasted 2 h (median, typically 48 min–9.5 h; 82 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.
Reachable from all 4 regions we check from.
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 596 ms.
Maintenance
Service Under Maintenance Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 23:45 | 0 | 0.0 | 629 ms | 0 |
| 01:45 | 0 | 0.0 | 875 ms | 0 |
| 03:45 | 0 | 0.0 | 722 ms | 0 |
| 06:00 | 0 | 0.0 | 527 ms | 0 |
| 08:00 | 0 | 0.0 | 748 ms | 0 |
| 10:15 | 0 | 0.0 | 700 ms | 0 |
| 12:15 | 0 | 0.0 | 892 ms | 0 |
| 14:15 | 0 | 0.0 | 865 ms | 0 |
| 16:15 | 0 | 0.0 | 1062 ms | 0 |
| 17:15 | 0 | 0.0 | 859 ms | 0 |
| 18:45 | 0 | 0.0 | 443 ms | 0 |
| 19:45 | 0 | 0.0 | 857 ms | 0 |
| 20:15 | 0 | 0.0 | 743 ms | 0 |
| 22:15 | 0 | 0.0 | 596 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.
Oppgradering av lønnssystemet 2026
2026 Oppgradering av lønnssystemet Flere av DFØ sine systemer vil være utilgjengelige for alle brukere mellom fredag 20. november kl. 16.00 og mandag 23. november kl. 07.00 på grunn av en teknisk oppgradering. SAP programvare skal oppgraderes. Dette betyr at følgende systemer vil være utilgjengelige i perioder for alle brukere under oppgraderingen: • Selvbetjening for ansatte og ledere •…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for DFO yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when DFO goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send DFO alerts to Slack, Discord or a webhook — free.
We track DFO (dfo.no) as part of the Cloud & developer group. Direktoratet for forvaltning og økonomistyring (DFØ) er statens fagorgan for økonomistyring, gode beslutningsgrunnlag for statlige tiltak, organisering og ledelse i staten, og anskaffelser i offentlig sektor, og leverer lønns- og regnskapstjenester.
DFO publishes an official status page at status.dfo.no; when we can read it, its incident level is folded into the status shown here.
Common problems for 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. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 751 ms average, 443–1062 ms range across 14 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
We have not recorded a public DFO incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
751 ms on average over the last 24 hours (443–1062 ms). Latest regional checks: US East 520 ms, US West 642 ms, Europe 92 ms, Asia-Pacific 1121 ms.
Yes, at https://status.dfo.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 DFO here at once, the problem is on DFO'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 DFO. 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.