User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 519 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 14:45 | 0 | 0.0 | 637 ms | 0 |
| 16:45 | 0 | 0.0 | 763 ms | 0 |
| 19:00 | 0 | 0.0 | 481 ms | 0 |
| 21:00 | 0 | 0.0 | 527 ms | 0 |
| 23:00 | 0 | 0.0 | 549 ms | 0 |
| 01:00 | 0 | 0.0 | 601 ms | 0 |
| 03:15 | 0 | 0.0 | 578 ms | 0 |
| 05:15 | 0 | 0.0 | 429 ms | 0 |
| 07:30 | 0 | 0.0 | 506 ms | 0 |
| 09:30 | 0 | 0.0 | 441 ms | 0 |
| 11:30 | 0 | 0.0 | 519 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 6 days of data so far, so the 90-day numbers fill in over time.
No outages on record for NO-Q 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 NO-Q goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send NO-Q alerts to Slack, Discord or a webhook — free.
NO-Q, at no-q.info, is one of the Productivity services we monitor. No-Q Plattform für ressourcen- und kapazitätsgesteuerte Online-Terminbuchung No-Q hilft Ihnen dabei, Ihre Dienstleistungen kompetent zu planen, benutzerfreundlich und schnell abzuwickeln, Arbeitsprozesse zu optimieren, zu digitalisieren und Ihr Unternehmen effizient zu verwalten. Kostenlose Produktdemo anfragen No-Q ist eine Softwarelösung für die kapazitätsgesteuerte Terminkoordinierung in Gesundheitseinrichtungen, Unternehmen und der öffentlichen Verwaltung. No-Q ist Cloud-basiert und bietet
NO-Q publishes an official status page at status.no-q.info; when we can read it, its incident level is folded into the status shown here.
Common problems for productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 545 ms average, 429–763 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public NO-Q incident since monitoring began 6 days ago.
From our own checks: 100% over 6 days of checks.
545 ms on average over the last 24 hours (429–763 ms).
Yes, at https://status.no-q.info.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report NO-Q here at once, the problem is on NO-Q'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 NO-Q. 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.