Ops One AG platform status and maintenance announcements. Times are indicated in local Swiss time. https://opsone.ch/.
All systems are operational
Scheduled Maintenance
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

Sentry 26.4.1

We will update Sentry to version 26.4.1.

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 29th January 2019

NextCloud Update v15.0.2, scheduled 7 years ago

We will update NextCloud to Version v15.0.2. We expect a downtime of ~10 minutes.

Start maintenance window: 29/01/2019 00:00 CEST
Stop maintenance window: 29/01/2019 02:00 CEST

Tuesday 22nd January 2019

Mailserver Update, scheduled 7 years ago

We perform software updates on our mail servers. We expect a downtime of ~5 minutes.

Start maintenance window: 22/01/2019 00:00
Stop maintenance window: 22/01/2019 01:30

New features / Changes:

  • [Dovecot] Add more special_use folder names
  • [ClamAV] Fix whitelist permission error
  • [Compose] Update ClamAV and SOGo images

Monday 21st January 2019

No incidents reported

Sunday 20th January 2019

No incidents reported

Saturday 19th January 2019

No incidents reported

Friday 18th January 2019

No incidents reported

Thursday 17th January 2019

Managed Server Version 5 & 6: TLS/SSH Diffie-Hellman group updated, scheduled 7 years ago

In course of our half-yearly security checks, we updated the globally used Diffie-Hellman group to a new set for TLS and SSH.

Wednesday 16th January 2019

Managed Server Version 6: Add Support for Solr 7 and Remove Outdated Solr Versions
  • added support for Solr 7, see documentation for details
  • removed support for Solr 5
  • removed support for Solr 4
  • removed tomcat service which is not used anymore

Reference #498

Tuesday 15th January 2019

No incidents reported

Monday 14th January 2019

Managed Server Version 6: Website Service: Enable ModSecurity in DetectionOnly Mode

So far, there was no web application firewall on generation 6 servers, as we had yet to lay some groundwork before. With this change, we will enable ModSecurity and load the OWASP core set, please see the detailed changes below:

  • update nginx to the latest stable version 1.14.2
  • load ModSecurity base configuration
  • load OWASP core rule set
  • enable ModSecurity in DetectionOnly mode (= logging only)
  • detected requests are logged into the ModSecurity audit log at /var/log/nginx/modsecurity.log (accessible via devop user)

Next steps:

  • we will analyze all audit logs and take appropriate actions if required
  • we might contact you over the next 2 weeks to discuss required changes on our or your end if required
  • we're going to activate blocking mode (switch engine from DetectionOnly to on) on Monday, January 28th

Reference: #291