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 628 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 506 ms | 0 |
| Nov 7 | 0 | 0.0 | 264 ms | 0 |
| Nov 7 | 0 | 0.0 | 569 ms | 0 |
| Nov 7 | 0 | 0.0 | 392 ms | 0 |
| Nov 7 | 0 | 0.0 | 804 ms | 0 |
| Nov 8 | 0 | 0.0 | 337 ms | 0 |
| Nov 8 | 0 | 0.0 | 396 ms | 0 |
| Nov 8 | 0 | 0.0 | 374 ms | 0 |
| Nov 8 | 0 | 0.0 | 398 ms | 0 |
| Nov 9 | 0 | 0.0 | 555 ms | 0 |
| Nov 9 | 0 | 0.0 | 385 ms | 0 |
| Nov 9 | 0 | 0.0 | 437 ms | 0 |
| Nov 9 | 0 | 0.0 | 416 ms | 0 |
| Nov 10 | 0 | 0.0 | 391 ms | 0 |
| Nov 10 | 0 | 0.0 | 523 ms | 0 |
| Nov 10 | 0 | 0.0 | 454 ms | 0 |
| Nov 10 | 0 | 0.0 | 566 ms | 0 |
| Nov 11 | 0 | 0.0 | 421 ms | 0 |
| Nov 11 | 0 | 0.0 | 360 ms | 0 |
| Nov 11 | 0 | 0.0 | 460 ms | 0 |
| Nov 11 | 0 | 0.0 | 373 ms | 0 |
| Nov 12 | 0 | 0.0 | 480 ms | 0 |
| Nov 12 | 0 | 0.0 | 463 ms | 0 |
| Nov 12 | 0 | 0.0 | 445 ms | 0 |
| Nov 12 | 0 | 0.0 | 351 ms | 0 |
| Nov 13 | 0 | 0.0 | 384 ms | 0 |
| Nov 13 | 0 | 0.0 | 416 ms | 0 |
| Nov 13 | 0 | 0.0 | 392 ms | 0 |
| Nov 13 | 0 | 0.0 | 436 ms | 0 |
| Nov 14 | 0 | 0.0 | 348 ms | 0 |
| Nov 14 | 0 | 0.0 | 441 ms | 0 |
| Nov 14 | 0 | 0.0 | 286 ms | 0 |
| Nov 14 | 0 | 0.0 | 436 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.
No outages on record for Folkehelseinstituttet 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 Folkehelseinstituttet goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track Folkehelseinstituttet (fhi.no) as part of the Cloud & developer group. Folkehelseinstituttet har nasjonale oppgaver innen blant annet smittevern, psykisk og fysisk helse, miljømedisin, epidemiologi og rusmidler.
Folkehelseinstituttet publishes an official status page at status.fhi.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. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 392 ms average, 205–628 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Folkehelseinstituttet incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
392 ms on average over the last 24 hours (205–628 ms).
Yes, at https://status.fhi.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 Folkehelseinstituttet here at once, the problem is on Folkehelseinstituttet'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 Folkehelseinstituttet. 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.