User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Smart home
Is Qbee down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
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 → qbee.io—
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 3 min ago. Last stored result reached it in 76 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 19 | 0 | 0.0 | 38 ms | 0 |
| Mon 21 | 0 | 0.0 | 120 ms | 0 |
| Mon 23 | 0 | 0.0 | 59 ms | 0 |
| Tue 01 | 0 | 0.0 | 110 ms | 0 |
| Tue 03 | 0 | 0.0 | 97 ms | 0 |
| Tue 05 | 0 | 0.0 | 55 ms | 0 |
| Tue 07 | 0 | 0.0 | 93 ms | 0 |
| Tue 09 | 0 | 0.0 | 81 ms | 0 |
| Tue 12 | 0 | 0.0 | 42 ms | 0 |
| Tue 14 | 0 | 0.0 | 57 ms | 0 |
| Tue 16 | 0 | 0.0 | 41 ms | 0 |
| Tue 18 | 0 | 0.0 | 212 ms | 0 |
| Tue 21 | 0 | 0.0 | 84 ms | 0 |
| Tue 23 | 0 | 0.0 | 51 ms | 0 |
| Wed 01 | 0 | 0.0 | 61 ms | 0 |
| Wed 03 | 0 | 0.0 | 62 ms | 0 |
| Wed 06 | 0 | 0.0 | 58 ms | 0 |
| Wed 08 | 0 | 0.0 | 30 ms | 0 |
| Wed 10 | 0 | 0.0 | 71 ms | 0 |
| Wed 12 | 0 | 0.0 | 47 ms | 0 |
| Wed 14 | 0 | 0.0 | 73 ms | 0 |
| Wed 16 | 0 | 0.0 | 65 ms | 0 |
| Wed 19 | 0 | 0.0 | 95 ms | 0 |
| Wed 21 | 0 | 0.0 | 112 ms | 0 |
| Wed 23 | 0 | 0.0 | 76 ms | 0 |
| Thu 01 | 0 | 0.0 | 112 ms | 0 |
| Thu 03 | 0 | 0.0 | 68 ms | 0 |
| Thu 05 | 0 | 0.0 | 60 ms | 0 |
| Thu 07 | 0 | 0.0 | 107 ms | 0 |
| Thu 09 | 0 | 0.0 | 29 ms | 0 |
| Thu 12 | 0 | 0.0 | 60 ms | 0 |
| Thu 14 | 0 | 0.0 | 91 ms | 0 |
| Thu 16 | 0 | 0.0 | 135 ms | 0 |
| Thu 18 | 0 | 0.0 | 77 ms | 0 |
| Thu 20 | 0 | 0.0 | 80 ms | 0 |
| Thu 21 | 0 | 0.0 | 59 ms | 0 |
| Thu 23 | 0 | 0.0 | 94 ms | 0 |
| Fri 01 | 0 | 0.0 | 78 ms | 0 |
| Fri 03 | 0 | 0.0 | 83 ms | 0 |
| Fri 04 | 0 | 0.0 | 60 ms | 0 |
| Fri 05 | 0 | 0.0 | 147 ms | 0 |
| Fri 08 | 0 | 0.0 | 55 ms | 0 |
| Fri 10 | 0 | 0.0 | 54 ms | 0 |
| Fri 11 | 0 | 0.0 | 45 ms | 0 |
| Fri 12 | 0 | 0.0 | 46 ms | 0 |
| Fri 15 | 0 | 0.0 | 76 ms | 0 |
| Fri 17 | 0 | 0.0 | 85 ms | 0 |
| Fri 18 | 0 | 0.0 | 76 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 Qbee badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
This week
Planned maintenance
Database maintenance
As part of our regular security and stability maintenance, we will be applying a required patch to the Qbee database cluster during this window. Applying the patch requires a restart of the database cluster. We expect the actual interruption to last around one minute, but have reserved a 30-minute window to allow for verification afterwards. During the restart, the web interface and API may be…
Announced by Qbee · source
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
Past outages
No outages on record for Qbee yet. Outages of 10 minutes or more get their own page here.
Having trouble with Qbee?
One report per service every 10 minutes from this network. No account.
Follow Qbee
Get an email when Qbee goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qbee alerts to Slack, Discord or a webhook — free.
About Qbee
Qbee is listed in our Smart home category and checked at qbee.io. Qbee is a unified operations platform for IoT devices and intelligent edge infrastructure, with OTA updates, automation, monitoring and secure remote access.
Qbee publishes an official status page at status.qbee.io; when we can read it, its incident level is folded into the status shown here.
Typical issues with smart home services: devices showing offline, app control failing, and automations not running.
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: 74 ms average, 45–147 ms range across 14 successful checks.
Questions
Is Qbee down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Qbee last down?
We have not recorded a public Qbee incident since monitoring began 8 days ago.
What is Qbee's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Qbee respond?
74 ms on average over the last 24 hours (45–147 ms).
Does Qbee have an official status page?
Yes, at https://status.qbee.io.
Qbee 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 smart home services, watch for devices showing offline, app control failing, and automations not running. If many people report Qbee here at once, the problem is on Qbee'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 Qbee. 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.