User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
mittanbud.no · 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 57 min ago. Last stored result reached it in 916 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 657 ms | 0 |
| Tue 14 | 0 | 0.0 | 815 ms | 0 |
| Tue 16 | 0 | 0.0 | 759 ms | 0 |
| Tue 19 | 0 | 0.0 | 743 ms | 0 |
| Tue 21 | 0 | 0.0 | 1009 ms | 0 |
| Tue 23 | 0 | 0.0 | 857 ms | 0 |
| Wed 01 | 0 | 0.0 | 712 ms | 0 |
| Wed 03 | 0 | 0.0 | 786 ms | 0 |
| Wed 06 | 0 | 0.0 | 660 ms | 0 |
| Wed 08 | 0 | 0.0 | 731 ms | 0 |
| Wed 10 | 0 | 0.0 | 732 ms | 0 |
| Wed 12 | 0 | 0.0 | 660 ms | 0 |
| Wed 14 | 0 | 0.0 | 742 ms | 0 |
| Wed 17 | 0 | 0.0 | 1197 ms | 0 |
| Wed 19 | 0 | 0.0 | 672 ms | 0 |
| Wed 21 | 0 | 0.0 | 487 ms | 0 |
| Wed 23 | 0 | 0.0 | 734 ms | 0 |
| Thu 01 | 0 | 0.0 | 759 ms | 0 |
| Thu 03 | 0 | 0.0 | 730 ms | 0 |
| Thu 04 | 0 | 0.0 | 777 ms | 0 |
| Thu 06 | 0 | 0.0 | 797 ms | 0 |
| Thu 08 | 0 | 0.0 | 798 ms | 0 |
| Thu 10 | 0 | 0.0 | 1191 ms | 0 |
| Thu 13 | 0 | 0.0 | 709 ms | 0 |
| Thu 15 | 0 | 0.0 | 725 ms | 0 |
| Thu 17 | 0 | 0.0 | 815 ms | 0 |
| Thu 19 | 0 | 0.0 | 685 ms | 0 |
| Thu 21 | 0 | 0.0 | 817 ms | 0 |
| Thu 23 | 0 | 0.0 | 918 ms | 0 |
| Fri 01 | 0 | 0.0 | 780 ms | 0 |
| Fri 03 | 0 | 0.0 | 711 ms | 0 |
| Fri 05 | 0 | 0.0 | 755 ms | 0 |
| Fri 07 | 0 | 0.0 | 979 ms | 0 |
| Fri 09 | 0 | 0.0 | 729 ms | 0 |
| Fri 10 | 0 | 0.0 | 769 ms | 0 |
| Fri 12 | 0 | 0.0 | 750 ms | 0 |
| Fri 14 | 0 | 0.0 | 767 ms | 0 |
| Fri 16 | 0 | 0.0 | 705 ms | 0 |
| Fri 17 | 0 | 0.0 | 695 ms | 0 |
| Fri 19 | 0 | 0.0 | 700 ms | 0 |
| Fri 20 | 0 | 0.0 | 653 ms | 0 |
| Fri 22 | 0 | 0.0 | 946 ms | 0 |
| Sat 00 | 0 | 0.0 | 871 ms | 0 |
| Sat 02 | 0 | 0.0 | 1069 ms | 0 |
| Sat 03 | 0 | 0.0 | 748 ms | 0 |
| Sat 04 | 0 | 0.0 | 707 ms | 0 |
| Sat 05 | 0 | 0.0 | 1037 ms | 0 |
| Sat 07 | 0 | 0.0 | 916 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.
No outages on record for Mittanbud 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 Mittanbud goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Mittanbud alerts to Slack, Discord or a webhook — free.
Mittanbud is listed in our Cloud & developer category and checked at mittanbud.no. Har du en jobb du vil få utført? Legg ut jobben på Mittanbud og bli kontaktet av flere håndverkere med riktig kompetanse i ditt nærområde!
Mittanbud publishes an official status page at status.mittanbud.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 804 ms average, 653–1069 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Mittanbud incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
804 ms on average over the last 24 hours (653–1069 ms).
Yes, at https://status.mittanbud.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 Mittanbud here at once, the problem is on Mittanbud'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 Mittanbud. 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.