User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
digipost.no · Cloud & developer
Is Digipost down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Correction: On Nov 10, 2026 we retracted an incident report for Digipost published in error on Nov 10, 2026. No outage occurred. Read the retraction →
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 → digipost.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 821 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 |
|---|---|---|---|---|
| Mon 16 | 0 | 0.0 | 991 ms | 0 |
| Mon 18 | 0 | 0.0 | 851 ms | 0 |
| Mon 20 | 0 | 0.0 | 653 ms | 0 |
| Mon 23 | 0 | 0.0 | 795 ms | 0 |
| Tue 01 | 0 | 0.0 | 815 ms | 0 |
| Tue 03 | 0 | 0.0 | 847 ms | 0 |
| Tue 05 | 0 | 0.0 | 668 ms | 0 |
| Tue 07 | 0 | 0.0 | 606 ms | 0 |
| Tue 09 | 0 | 0.0 | 832 ms | 0 |
| Tue 11 | 0 | 0.0 | 800 ms | 0 |
| Tue 13 | 0 | 0.0 | 704 ms | 0 |
| Tue 16 | 0 | 0.0 | 441 ms | 0 |
| Tue 18 | 0 | 0.0 | 675 ms | 0 |
| Tue 20 | 0 | 0.0 | 690 ms | 0 |
| Tue 22 | 0 | 0.0 | 660 ms | 0 |
| Wed 01 | 0 | 0.0 | 718 ms | 0 |
| Wed 03 | 0 | 0.0 | 623 ms | 0 |
| Wed 05 | 0 | 0.0 | 1060 ms | 0 |
| Wed 07 | 0 | 0.0 | 602 ms | 0 |
| Wed 10 | 0 | 0.0 | 625 ms | 0 |
| Wed 12 | 0 | 0.0 | 649 ms | 0 |
| Wed 14 | 0 | 0.0 | 853 ms | 0 |
| Wed 16 | 0 | 0.0 | 888 ms | 0 |
| Wed 18 | 0 | 0.0 | 809 ms | 0 |
| Wed 20 | 0 | 0.0 | 615 ms | 0 |
| Wed 23 | 0 | 0.0 | 795 ms | 0 |
| Thu 01 | 0 | 0.0 | 688 ms | 0 |
| Thu 03 | 0 | 0.0 | 691 ms | 0 |
| Thu 05 | 0 | 0.0 | 700 ms | 0 |
| Thu 07 | 0 | 0.0 | 715 ms | 0 |
| Thu 09 | 0 | 0.0 | 775 ms | 0 |
| Thu 11 | 0 | 0.0 | 1079 ms | 0 |
| Thu 13 | 0 | 0.0 | 806 ms | 0 |
| Thu 15 | 0 | 0.0 | 688 ms | 0 |
| Thu 17 | 0 | 0.0 | 597 ms | 0 |
| Thu 19 | 0 | 0.0 | 850 ms | 0 |
| Thu 21 | 0 | 0.0 | 788 ms | 0 |
| Thu 23 | 0 | 0.0 | 642 ms | 0 |
| Fri 01 | 0 | 0.0 | 670 ms | 0 |
| Fri 04 | 0 | 0.0 | 624 ms | 0 |
| Fri 06 | 0 | 0.0 | 837 ms | 0 |
| Fri 08 | 0 | 0.0 | 859 ms | 0 |
| Fri 10 | 0 | 0.0 | 618 ms | 0 |
| Fri 12 | 0 | 0.0 | 730 ms | 0 |
| Fri 14 | 0 | 0.0 | 933 ms | 0 |
| Fri 16 | 0 | 0.0 | 693 ms | 0 |
| Fri 17 | 0 | 0.0 | 755 ms | 0 |
| Fri 19 | 0 | 0.0 | 821 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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Digipost 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 Digipost yet. Outages of 10 minutes or more get their own page here.
Having trouble with Digipost?
One report per service every 10 minutes from this network. No account.
Follow Digipost
Get an email when Digipost goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Digipost alerts to Slack, Discord or a webhook — free.
About Digipost
We track Digipost (digipost.no) as part of the Cloud & developer group. Få full oversikt over posten din på ett sted med Digipost. En trygg og effektiv løsning for å motta og oppbevare viktig post digitalt. Kom i gang enkelt og raskt!
Digipost publishes an official status page at status.digipost.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 748 ms average, 618–933 ms range across 12 successful checks.
Questions
Is Digipost down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Digipost last down?
We have not recorded a public Digipost incident since monitoring began 8 days ago.
What is Digipost's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Digipost respond?
748 ms on average over the last 24 hours (618–933 ms).
Does Digipost have an official status page?
Yes, at https://status.digipost.no.
Digipost 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 Digipost here at once, the problem is on Digipost'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 Digipost. 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.