New Multi-region uptime checks and custom-domain status pages

Q-CTRL Outage History

Daily provider-status observations and published incident history for Q-CTRL.

Operational

Q-CTRL is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Q-CTRL for future changes.

100% of 35 verified observed days had no reported provider issue

90-Day Trend

Jul 3Sep 30

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 100% 28 0

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 2 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.

Legacy Incident Archive

1 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

June 2026
Regression in authentication with Boulder Opal Toolkit client
minor Source not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue. If you are encountering errors authenticating the Boulder Opal Toolkit or Fire Opal Client please clear locally cached authentication tokens in `~/.config/qctrl` and try again.
identified
The issue has been identified and is being investigated further. If you are encountering errors authenticating the Boulder Opal Toolkit or Fire Opal Client please clear locally cached authentication tokens in `~/.config/qctrl` and try again.
investigating
We are currently investigating an issue with the Boulder Opal Toolkit client package which is affecting authentication.