Ops One AG platform status and maintenance announcements. Times are indicated in local Swiss time. https://opsone.ch/.
All systems are operational
Scheduled Maintenance
Managed Server 10: Debian Updates

We will update the following packages to the latest version.

  • libngtcp2-16=1.11.0-1+deb13u1
  • libngtcp2-crypto-gnutls8=1.11.0-1+deb13u1

Start maintenance window: 22/04/2026 23:00
Stop maintenance window: 23/04/2026 02:00

GitLab 18.10.4

We will update GitLab to version 18.10.4.

Reference: #1035

Start maintenance window: 22/04/2026 23:00
Stop maintenance window: 23/04/2026 02:00

Update GitLab Runner 18.11.1

We will update GitLab Runner to version 18.11.1.

Reference: #104

Start maintenance window: 27/04/2026 23:00
Stop maintenance window: 28/04/2026 02:00

LimeSurvey 6.16.17

We will update LimeSurvey to version 6.16.17.

Reference: #87

Start maintenance window: 27/04/2026 23:00
Stop maintenance window: 28/04/2026 02:00

Matomo 5.9.0

We will update Matomo to version 5.9.0.

Start maintenance window: 27/04/2026 23:00
Stop maintenance window: 28/04/2026 02:00

GitLab: Migration to new Container Registry Metadata-Database

GitLab comes with a new Metadata Database for the Container Registry that offers improved performance and new features that are not available in the legacy metadata storage.

We'll migrate all existing Managed GitLab installations to the new Metadata Database. This requires at least a restart of each GitLab installation followed by a one-time migration of the existing registry data.

The duration of this migration depends on the amount of existing data in the container registry that needs to be processed and can span from just a few minutes up approximately an hour. During this migration the registry is in read-only mode, but GitLab itself remains fully usable.

Start maintenance window: 29/04/2026 22:00
Stop maintenance window: 30/04/2026 02:00

GitLab: Migration to new Container Registry Metadata-Database

GitLab comes with a new Metadata Database for the Container Registry that offers improved performance and new features that are not available in the legacy metadata storage.

We'll migrate all existing Managed GitLab installations to the new Metadata Database. This requires at least a restart of each GitLab installation followed by a one-time migration of the existing registry data.

The duration of this migration depends on the amount of existing data in the container registry that needs to be processed and can span from just a few minutes up approximately an hour. During this migration the registry is in read-only mode, but GitLab itself remains fully usable.

Start maintenance window: 30/04/2026 22:00
Stop maintenance window: 01/05/2026 02:00

Past Incidents

Tuesday 14th May 2019

Cockpit: Version 1.4.0
  • #360 [FEATURE] display server status checks for generation 6
  • #364 [FEATURE] clarify SSH key label
  • #368 [FEATURE] disable main dns zone modifications
  • #370 [FEATURE] external billing flag per customer
  • #363 [TASK] do not show generation on common servers
  • #373 [TASK] disallow / in website hostname validation
  • #361 [BUGFIX] CI configuration: status update publication with special characters
  • #371 [BUGFIX] CI configuration: replace tar by bsdtar to work around OverlayFS bug
  • #372 [BUGFIX] follow-up #355 website model: add disableMonitoring property

Monday 13th May 2019

Managed Server Version 5: manually trigger server reboot through devop account, scheduled 6 years ago

It can make sense to reboot a server manually under some circumstances, for example if the load raises too high for further debugging. To enable you to issue such reboots by yourself, we allow the reboot alias command for the devop user as of now.

Reference #578

Managed Server Version 6: manually trigger server reboot through devop account, scheduled 6 years ago

It can make sense to reboot a server manually under some circumstances, for example if the load raises too high for further debugging. To enable you to issue such reboots by yourself, we allow the reboot alias command for the devop user as of now.

Reference #578

Update Discourse 2.2.5, scheduled 6 years ago

We will update Discourse to version 2.2.5.

Due to the inplace upgrade feature of Discourse, no downtime will be required.

Start maintenance window: 13/05/2018 10:00 CEST
Stop maintenance window: 13/05/2018 10:15 CEST

Sunday 12th May 2019

No incidents reported

Saturday 11th May 2019

No incidents reported

Friday 10th May 2019

No incidents reported

Thursday 9th May 2019

No incidents reported

Wednesday 8th May 2019

Managed Server Version 6: Announcing TYPO3 v9.5.6 and v8.7.25 security releases, scheduled 6 years ago

The TYPO3 Community announces the releases of TYPO3 v9.5.6 LTS and v8.7.25 LTS, as scheduled.

All versions are security releases and contain important security fixes - read the corresponding security advisories here:

  • https://typo3.org/security/advisory/typo3-core-sa-2019-009/
  • https://typo3.org/security/advisory/typo3-core-sa-2019-010/
  • https://typo3.org/security/advisory/typo3-core-sa-2019-011/
  • https://typo3.org/security/advisory/typo3-core-sa-2019-012/
  • https://typo3.org/security/advisory/typo3-core-sa-2019-013/

For details about the releases, please visit the following website:

  • https://typo3.org/article/typo3-956-and-8725-security-releases-published/