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 1231 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 1138 ms | 0 |
| Nov 7 | 0 | 0.0 | 1528 ms | 0 |
| Nov 7 | 0 | 0.0 | 1178 ms | 0 |
| Nov 7 | 0 | 0.0 | 1353 ms | 0 |
| Nov 8 | 0 | 0.0 | 1331 ms | 0 |
| Nov 8 | 0 | 0.0 | 1205 ms | 0 |
| Nov 8 | 0 | 0.0 | 1327 ms | 0 |
| Nov 8 | 0 | 0.0 | 1309 ms | 0 |
| Nov 9 | 0 | 0.0 | 1273 ms | 0 |
| Nov 9 | 0 | 0.0 | 1165 ms | 0 |
| Nov 9 | 0 | 0.0 | 1260 ms | 0 |
| Nov 9 | 0 | 0.0 | 1168 ms | 0 |
| Nov 10 | 0 | 0.0 | 1395 ms | 0 |
| Nov 10 | 0 | 0.0 | 1184 ms | 0 |
| Nov 10 | 0 | 0.0 | 1396 ms | 0 |
| Nov 10 | 0 | 0.0 | 1270 ms | 0 |
| Nov 11 | 0 | 0.0 | 1331 ms | 0 |
| Nov 11 | 0 | 0.0 | 591 ms | 0 |
| Nov 11 | 0 | 0.0 | 1198 ms | 0 |
| Nov 11 | 0 | 0.0 | 1089 ms | 0 |
| Nov 12 | 0 | 0.0 | 1312 ms | 0 |
| Nov 12 | 0 | 0.0 | 1221 ms | 0 |
| Nov 12 | 0 | 0.0 | 1091 ms | 0 |
| Nov 12 | 0 | 0.0 | 1439 ms | 0 |
| Nov 13 | 0 | 0.0 | 1342 ms | 0 |
| Nov 13 | 0 | 0.0 | 1236 ms | 0 |
| Nov 13 | 0 | 0.0 | 1246 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 8 days of data so far, so the 90-day numbers fill in over time.
Planlagt vedlikehold av mailservere for kernel-oppgradering
Vi vil gjennomføre et planlagt vedlikehold av 5 mailservere for en kernel-oppgradering. Under vedlikeholdsvinduet vil e-posttjenesten tidvis være utilgjengelig og det estimeres 20 minutter driftsavbrudd per server. Vi beklager ulempene dette måtte medføre. Ta gjerne kontakt med oss dersom dere har spørsmål.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Uniweb 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 Uniweb goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Uniweb alerts to Slack, Discord or a webhook — free.
Uniweb, at uniweb.no, is one of the Cloud & developer services we monitor. Norsk leverandør av hosting, domener, nettsidebygger og e-post. 25+ års erfaring. 99.99% oppetid. Uniweb – Nettsider gjort enkelt.
Uniweb publishes an official status page at status.uniweb.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 1206 ms average, 169–1489 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Uniweb incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
1206 ms on average over the last 24 hours (169–1489 ms).
Yes, at https://status.uniweb.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 Uniweb here at once, the problem is on Uniweb'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 Uniweb. 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.