Q-CTRL Outage History

Q-CTRL is up right now

Q-CTRL had 7 outages in the last 2 years totaling 72h 34m of downtime — averaging 0.3 incidents per month.

There were 7 Q-CTRL outages since September 4, 2024 totaling 72h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.q-ctrl.com

Minor June 19, 2026

Regression in authentication with Boulder Opal Toolkit client

Detected by Pingoru
Jun 19, 2026, 06:11 AM UTC
Resolved
Jun 21, 2026, 11:08 PM UTC
Duration
2d 16h
Affected: Q-CTRL Boulder OpalQ-CTRL Fire Opal
Timeline · 4 updates
  1. investigating Jun 19, 2026, 06:11 AM UTC

    We are currently investigating an issue with the Boulder Opal Toolkit client package which is affecting authentication.

  2. identified Jun 19, 2026, 06:28 AM UTC

    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.

  3. identified Jun 19, 2026, 06:29 AM UTC

    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.

  4. resolved Jun 21, 2026, 11:08 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Some product websites still affected by ongoing global outages

Detected by Pingoru
Oct 20, 2025, 10:03 PM UTC
Resolved
Oct 21, 2025, 02:42 AM UTC
Duration
4h 38m
Affected: Q-CTRL AccountsQ-CTRL Black Opal
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 10:03 PM UTC

    There is some degraded performance on some of our product websites due to ongoing issues with upstream cloud platform vendors. We are working to workaround these issues as well as monitoring them.

  2. monitoring Oct 21, 2025, 01:00 AM UTC

    We are continuing to monitor for further issues.

  3. resolved Oct 21, 2025, 02:42 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Issues with websites (include Boulder Opal, Fire Opal, account management)

Detected by Pingoru
Oct 20, 2025, 08:29 AM UTC
Resolved
Oct 20, 2025, 10:00 AM UTC
Duration
1h 30m
Affected: Q-CTRL AccountsQ-CTRL Black OpalQ-CTRL Boulder OpalQ-CTRL Fire OpalQ-CTRL Documentation
Timeline · 4 updates
  1. investigating Oct 20, 2025, 08:29 AM UTC

    We are currently investigating issues with a number of our product websites.

  2. identified Oct 20, 2025, 08:47 AM UTC

    The issue has been identified in upstream vendor cloud providers

  3. monitoring Oct 20, 2025, 08:48 AM UTC

    Our vendors report that systems are being recovered. We continue to monitor.

  4. resolved Oct 20, 2025, 10:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 29, 2025

Issues with Q-CTRL ID

Detected by Pingoru
Jun 29, 2025, 06:20 AM UTC
Resolved
Jun 29, 2025, 06:38 AM UTC
Duration
17m
Affected: Q-CTRL HomeQ-CTRL AccountsQ-CTRL Black OpalQ-CTRL Boulder OpalQ-CTRL Fire OpalQ-CTRL APIQ-CTRL DocumentationQ-CTRL ID
Timeline · 2 updates
  1. identified Jun 29, 2025, 07:13 AM UTC

    Users trying to access Q-CTRL ID may have experienced an error in account authentication. This will have blocked access to Q-CTRL products.

  2. resolved Jun 29, 2025, 07:15 AM UTC

    This incident has been resolved. All Q-CTRL products have been restored to operational order.

Read the full incident report →

Notice April 29, 2025

Issues with email verification

Detected by Pingoru
Apr 29, 2025, 06:28 AM UTC
Resolved
Apr 29, 2025, 06:28 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 30, 2025, 07:15 AM UTC

    New users that signed up may not have received an email to verify their accounts. This issue has been resolved and all impacted users should have received another email to verify their account and access Q-CTRL products.

Read the full incident report →

Major March 14, 2025

Fire Opal response error

Detected by Pingoru
Mar 14, 2025, 06:41 AM UTC
Resolved
Mar 14, 2025, 07:15 AM UTC
Duration
33m
Affected: Q-CTRL Fire Opal
Timeline · 4 updates
  1. investigating Mar 14, 2025, 06:41 AM UTC

    We are currently investigating an issue affecting customer using Fire Opal with IBM

  2. identified Mar 14, 2025, 07:03 AM UTC

    The issue has been identified and we are working towards a resolution.

  3. monitoring Mar 14, 2025, 07:11 AM UTC

    We are continuing to monitor the system which is under increased load. Customers using Fire Opal may experience a delay in response times during this period.

  4. resolved Mar 14, 2025, 07:15 AM UTC

    Fire Opal is operating as normal

Read the full incident report →

Critical January 7, 2025

Q-CTRL Front-End websites affected

Detected by Pingoru
Jan 07, 2025, 02:38 AM UTC
Resolved
Jan 07, 2025, 03:15 AM UTC
Duration
36m
Affected: Q-CTRL HomeQ-CTRL AccountsQ-CTRL Black OpalQ-CTRL Boulder OpalQ-CTRL ID
Timeline · 2 updates
  1. identified Jan 07, 2025, 03:10 AM UTC

    We are undergoing an outage at the moment and working to resolve the issue as soon as possible. During this time, access to Q-CTRL clients (Accounts, Black Opal, Boulder Opal and ID) will be impacted. We apologize for any inconvenience this may cause and seek your patience. If you have any questions or concerns, please do not hesitate to reach out to [email protected].

  2. resolved Jan 07, 2025, 03:15 AM UTC

    This incident has now been resolved.

Read the full incident report →