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 53 min ago. Last stored result reached it in 899 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 1209 ms | 0 |
| Mon 17 | 0 | 0.0 | 1101 ms | 0 |
| Mon 19 | 0 | 0.0 | 1086 ms | 0 |
| Mon 21 | 0 | 0.0 | 1428 ms | 0 |
| Mon 23 | 0 | 0.0 | 953 ms | 0 |
| Tue 01 | 0 | 0.0 | 1035 ms | 0 |
| Tue 03 | 0 | 0.0 | 1490 ms | 0 |
| Tue 06 | 0 | 0.0 | 1283 ms | 0 |
| Tue 08 | 0 | 0.0 | 1294 ms | 0 |
| Tue 10 | 0 | 0.0 | 1297 ms | 0 |
| Tue 12 | 0 | 0.0 | 718 ms | 0 |
| Tue 14 | 0 | 0.0 | 2595 ms | 0 |
| Tue 16 | 0 | 0.0 | 685 ms | 0 |
| Tue 19 | 0 | 0.0 | 1110 ms | 0 |
| Tue 21 | 0 | 0.0 | 1112 ms | 0 |
| Tue 23 | 0 | 0.0 | 859 ms | 0 |
| Wed 01 | 0 | 0.0 | 641 ms | 0 |
| Wed 04 | 0 | 0.0 | 1388 ms | 0 |
| Wed 06 | 0 | 0.0 | 810 ms | 0 |
| Wed 08 | 0 | 0.0 | 1414 ms | 0 |
| Wed 10 | 0 | 0.0 | 942 ms | 0 |
| Wed 13 | 0 | 0.0 | 1149 ms | 0 |
| Wed 15 | 0 | 0.0 | 1159 ms | 0 |
| Wed 17 | 0 | 0.0 | 1009 ms | 0 |
| Wed 19 | 0 | 0.0 | 815 ms | 0 |
| Wed 21 | 0 | 0.0 | 1393 ms | 0 |
| Wed 23 | 0 | 0.0 | 1246 ms | 0 |
| Thu 02 | 0 | 0.0 | 1109 ms | 0 |
| Thu 04 | 0 | 0.0 | 1308 ms | 0 |
| Thu 06 | 0 | 0.0 | 1067 ms | 0 |
| Thu 08 | 0 | 0.0 | 1012 ms | 0 |
| Thu 10 | 0 | 0.0 | 897 ms | 0 |
| Thu 12 | 0 | 0.0 | 813 ms | 0 |
| Thu 14 | 0 | 0.0 | 1378 ms | 0 |
| Thu 16 | 0 | 0.0 | 1102 ms | 0 |
| Thu 18 | 0 | 0.0 | 1386 ms | 0 |
| Thu 20 | 0 | 0.0 | 1124 ms | 0 |
| Thu 22 | 0 | 0.0 | 1378 ms | 0 |
| Fri 00 | 0 | 0.0 | 1384 ms | 0 |
| Fri 03 | 0 | 0.0 | 1268 ms | 0 |
| Fri 05 | 0 | 0.0 | 1362 ms | 0 |
| Fri 07 | 0 | 0.0 | 1262 ms | 0 |
| Fri 09 | 0 | 0.0 | 987 ms | 0 |
| Fri 10 | 0 | 0.0 | 1175 ms | 0 |
| Fri 12 | 0 | 0.0 | 1069 ms | 0 |
| Fri 14 | 0 | 0.0 | 578 ms | 0 |
| Fri 16 | 0 | 0.0 | 1426 ms | 0 |
| Fri 17 | 0 | 0.0 | 899 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 Qweb 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 Qweb goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qweb alerts to Slack, Discord or a webhook — free.
We track Qweb (qweb.nl) as part of the Cloud & developer group. Domeinen, webhosting en cloud uit Nederland — met razendsnelle servers en echte mensen aan de lijn. Al 25 jaar persoonlijke service.
Qweb publishes an official status page at status.qweb.nl; 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: 1173 ms average, 578–1426 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Qweb incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1173 ms on average over the last 24 hours (578–1426 ms).
Yes, at https://status.qweb.nl.
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 Qweb here at once, the problem is on Qweb'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 Qweb. 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.