User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
q-ctrl.com · Cloud & developer
Is Q-CTRL 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 → q-ctrl.com—
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 22 min ago. Last stored result reached it in 40 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 14 | 0 | 0.0 | 69 ms | 0 |
| Mon 16 | 0 | 0.0 | 1757 ms | 0 |
| Mon 18 | 0 | 0.0 | 96 ms | 0 |
| Mon 20 | 0 | 0.0 | 57 ms | 0 |
| Mon 22 | 0 | 0.0 | 78 ms | 0 |
| Tue 00 | 0 | 0.0 | 55 ms | 0 |
| Tue 02 | 0 | 0.0 | 53 ms | 0 |
| Tue 04 | 0 | 0.0 | 85 ms | 0 |
| Tue 06 | 0 | 0.0 | 67 ms | 0 |
| Tue 07 | 0 | 0.0 | 32 ms | 0 |
| Tue 09 | 0 | 0.0 | 111 ms | 0 |
| Tue 11 | 0 | 0.0 | 89 ms | 0 |
| Tue 13 | 0 | 0.0 | 75 ms | 0 |
| Tue 15 | 0 | 0.0 | 115 ms | 0 |
| Tue 17 | 0 | 0.0 | 122 ms | 0 |
| Tue 20 | 0 | 0.0 | 53 ms | 0 |
| Tue 22 | 0 | 0.0 | 69 ms | 0 |
| Wed 00 | 0 | 0.0 | 135 ms | 0 |
| Wed 02 | 0 | 0.0 | 42 ms | 0 |
| Wed 05 | 0 | 0.0 | 74 ms | 0 |
| Wed 07 | 0 | 0.0 | 29 ms | 0 |
| Wed 09 | 0 | 0.0 | 115 ms | 0 |
| Wed 11 | 0 | 0.0 | 33 ms | 0 |
| Wed 14 | 0 | 0.0 | 44 ms | 0 |
| Wed 16 | 0 | 0.0 | 93 ms | 0 |
| Wed 18 | 0 | 0.0 | 122 ms | 0 |
| Wed 20 | 0 | 0.0 | 41 ms | 0 |
| Wed 22 | 0 | 0.0 | 77 ms | 0 |
| Thu 00 | 0 | 0.0 | 149 ms | 0 |
| Thu 03 | 0 | 0.0 | 117 ms | 0 |
| Thu 05 | 0 | 0.0 | 105 ms | 0 |
| Thu 07 | 0 | 0.0 | 100 ms | 0 |
| Thu 09 | 0 | 0.0 | 66 ms | 0 |
| Thu 11 | 0 | 0.0 | 58 ms | 0 |
| Thu 13 | 0 | 0.0 | 118 ms | 0 |
| Thu 15 | 0 | 0.0 | 49 ms | 0 |
| Thu 17 | 0 | 0.0 | 39 ms | 0 |
| Thu 19 | 0 | 0.0 | 115 ms | 0 |
| Thu 21 | 0 | 0.0 | 99 ms | 0 |
| Thu 23 | 0 | 0.0 | 162 ms | 0 |
| Fri 01 | 0 | 0.0 | 87 ms | 0 |
| Fri 03 | 0 | 0.0 | 41 ms | 0 |
| Fri 05 | 0 | 0.0 | 72 ms | 0 |
| Fri 07 | 0 | 0.0 | 55 ms | 0 |
| Fri 09 | 0 | 0.0 | 43 ms | 0 |
| Fri 11 | 0 | 0.0 | 40 ms | 0 |
| Fri 13 | 0 | 0.0 | 67 ms | 0 |
| Fri 15 | 0 | 0.0 | 40 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 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Q-CTRL badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Q-CTRL yet. Outages of 10 minutes or more get their own page here.
Having trouble with Q-CTRL?
One report per service every 10 minutes from this network. No account.
Follow Q-CTRL
Get an email when Q-CTRL goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Q-CTRL alerts to Slack, Discord or a webhook — free.
About Q-CTRL
Q-CTRL, at q-ctrl.com, is one of the Cloud & developer services we monitor. Infrastructure software to power the quantum future. We expand the utility of quantum computers and deliver new quantum sensing capabilities through software.
Q-CTRL publishes an official status page at status.q-ctrl.com; when we can read it, its incident level is folded into the status shown here.
Typical issues 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: 69 ms average, 27–162 ms range across 13 successful checks.
Questions
Is Q-CTRL down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Q-CTRL last down?
We have not recorded a public Q-CTRL incident since monitoring began 7 days ago.
What is Q-CTRL's uptime?
From our own checks: 100% over 7 days of checks.
How fast does Q-CTRL respond?
69 ms on average over the last 24 hours (27–162 ms).
Does Q-CTRL have an official status page?
Yes, at https://status.q-ctrl.com.
Q-CTRL 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 cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Q-CTRL here at once, the problem is on Q-CTRL'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 Q-CTRL. 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.