All systems are operational
Maintenance
Migration impacting various managed components

On Friday starting at 22:00 we will be performing a migration impacting various managed components supporting our offering. The following services will be offline or impacted:

  • Secrets management
  • Cloudbear Mesh (VPN)
  • Cloudbear ID
  • DNS panel

Already connected clients to Cloudbear Mesh will continue to work, and you won't be able to sign into Cloudbear ID (and thus Cloudbear dashboarding). Existing login sessions will also continue to work for the duration of the session.

Deployments during these period is discouraged. If needed, please contact Cloudbear support through the means available to you.

Past Incidents

Monday 1st June 2026

Managed Kubernetes Kubernetes scaling limited because of Quay.io outage

There is an outage at the Quay.io container registry, because of this new nodes cannot pull necessary components, these nodes cannot become ready for this.

Thursday 28th May 2026

Managed Monitoring Grafana dashboarding offline

We're investigating.

  • We've found the issue and have deployed a fix, unfortunately Grafana had a memory leak.

  • We unfortunately continue to investigate the same outage.

  • We've upgraded the cluster.

  • We've increased capacity, we're monitoring the situation.

  • Unfortunately, Grafana is still having sporadic issues due to increased load. We're investigating.

  • A fix has rolled out.

    • Wednesday 20th May 2026

    Multiple platform issues

    We are investigating. Multiple platforms are having issues.

  • All primary and secondary platforms are stable and online, and all customer environments are fully operational. Most redundancy has been restored. Over the coming days we will continue working to restore full redundancy across all aspects, and further investigate the root cause in collaboration with our network hardware provider to deliver an RFO.

  • All critical services have been operational for some time now, we've recovered all customer environments to an operational state as well.

    We've started to recover non-critical services and ensure all redundancy is back in place.

  • We continue to restore services affected. Engineers are on-site to assist.

  • We are continuing to restore services affected.

  • The root cause has been found, a failing switch. We have restarted it, and it seems to work again.

    Later investigation will be held with the network hardware supplier into the the cause on why this caused so a so severe outage, since this switch is part of a redundant pair.

  • We are patching customer environments to work around the issue, while continued investigation is on its way to the root cause of the incident.

  • CBWS is experiencing a DNS outage on the legacy DNS servers. We are continuing investigating.