User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Folkehelseinstituttet down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → fhi.no—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · 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 243 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 18 | 0 | 0.0 | 566 ms | 0 |
| Tue 20 | 0 | 0.0 | 802 ms | 0 |
| Tue 23 | 0 | 0.0 | 260 ms | 0 |
| Wed 01 | 0 | 0.0 | 421 ms | 0 |
| Wed 03 | 0 | 0.0 | 648 ms | 0 |
| Wed 05 | 0 | 0.0 | 403 ms | 0 |
| Wed 08 | 0 | 0.0 | 300 ms | 0 |
| Wed 10 | 0 | 0.0 | 420 ms | 0 |
| Wed 12 | 0 | 0.0 | 460 ms | 0 |
| Wed 14 | 0 | 0.0 | 1202 ms | 0 |
| Wed 16 | 0 | 0.0 | 330 ms | 0 |
| Wed 18 | 0 | 0.0 | 258 ms | 0 |
| Wed 21 | 0 | 0.0 | 488 ms | 0 |
| Wed 23 | 0 | 0.0 | — | 0 |
| Thu 01 | 0 | 0.0 | 278 ms | 0 |
| Thu 03 | 0 | 0.0 | 480 ms | 0 |
| Thu 05 | 0 | 0.0 | 684 ms | 0 |
| Thu 07 | 0 | 0.0 | 301 ms | 0 |
| Thu 09 | 0 | 0.0 | 463 ms | 0 |
| Thu 11 | 0 | 0.0 | 584 ms | 0 |
| Thu 13 | 0 | 0.0 | 516 ms | 0 |
| Thu 15 | 0 | 0.0 | 445 ms | 0 |
| Thu 17 | 0 | 0.0 | 299 ms | 0 |
| Thu 19 | 0 | 0.0 | 448 ms | 0 |
| Thu 21 | 0 | 0.0 | 254 ms | 0 |
| Fri 00 | 0 | 0.0 | 377 ms | 0 |
| Fri 02 | 0 | 0.0 | 860 ms | 0 |
| Fri 04 | 0 | 0.0 | 384 ms | 0 |
| Fri 06 | 0 | 0.0 | 594 ms | 0 |
| Fri 08 | 0 | 0.0 | 456 ms | 0 |
| Fri 10 | 0 | 0.0 | 416 ms | 0 |
| Fri 11 | 0 | 0.0 | 377 ms | 0 |
| Fri 12 | 0 | 0.0 | 301 ms | 0 |
| Fri 14 | 0 | 0.0 | 506 ms | 0 |
| Fri 16 | 0 | 0.0 | 392 ms | 0 |
| Fri 17 | 0 | 0.0 | 352 ms | 0 |
| Fri 19 | 0 | 0.0 | 271 ms | 0 |
| Fri 20 | 0 | 0.0 | 566 ms | 0 |
| Fri 22 | 0 | 0.0 | 406 ms | 0 |
| Sat 00 | 0 | 0.0 | 492 ms | 0 |
| Sat 02 | 0 | 0.0 | 307 ms | 0 |
| Sat 04 | 0 | 0.0 | 287 ms | 0 |
| Sat 07 | 0 | 0.0 | 586 ms | 0 |
| Sat 08 | 0 | 0.0 | 441 ms | 0 |
| Sat 11 | 0 | 0.0 | 433 ms | 0 |
| Sat 13 | 0 | 0.0 | 321 ms | 0 |
| Sat 16 | 0 | 0.0 | 251 ms | 0 |
| Sat 18 | 0 | 0.0 | 243 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 Folkehelseinstituttet badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Folkehelseinstituttet yet. Outages of 10 minutes or more get their own page here.
Having trouble with Folkehelseinstituttet?
One report per service every 10 minutes from this network. No account.
Follow Folkehelseinstituttet
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.
About Folkehelseinstituttet
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: 400 ms average, 205–667 ms range across 13 successful checks.
Questions
Is Folkehelseinstituttet down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Folkehelseinstituttet last down?
We have not recorded a public Folkehelseinstituttet incident since monitoring began 9 days ago.
What is Folkehelseinstituttet's uptime?
From our own checks: 100% over 9 days of checks.
How fast does Folkehelseinstituttet respond?
400 ms on average over the last 24 hours (205–667 ms).
Does Folkehelseinstituttet have an official status page?
Yes, at https://status.fhi.no.
Folkehelseinstituttet 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 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.