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

Cluster Maintenance

We will update soft- and firmware throughout our cluster. During the update, a higher disk i/o latency is to be expected.

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 23rd October 2018

Mailserver Update, scheduled 7 years ago

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

Start maintenance window: 23/10/2018 00:00 CEST
Stop maintenance window: 23/10/2018 02:00 CEST

New features / Changes:

  • [Web] Feature: Allow to add more administrators
  • [Web] Feature: System mails (send mails to all mailboxes via LMTP)
  • [Web] Feature: TLS policy maps
  • [Postfix] Increase default message size limit to 100 MiB
  • [Dovecot] Set imap_max_line_length = 2 M
  • [Dovecot] Pull Spamassassin ruleset to be read by Rspamd (ruleset from Heinlein Support)
  • [Dovecot] Garbage collector for deleted maildirs
  • [Dovecot] Encrypt maildir with global key pair
  • [Compose] New images for Rspamd, PHP-FPM, SOGo, Dovecot, Docker API, Watchdog, ACME, Postfix, ClamAV, Unbound

Tuesday 16th October 2018

No incidents reported

Monday 15th October 2018

Update Discourse 2.1.2, scheduled 7 years ago

We will update Discourse to version 2.1.2.

Managed Server Version 5: PHP 7.1 and 7.2 updates, scheduled 7 years ago

PHP was updated to the following versions:

  • ops-php71/unknown 7.1.23-ops-8127 amd64 [upgradable from: 7.1.22-ops-7501]
  • ops-php72/unknown 7.2.11-ops-8123 amd64 [upgradable from: 7.2.10-ops-7497]

Sunday 14th October 2018

No incidents reported

Saturday 13th October 2018

No incidents reported

Friday 12th October 2018

No incidents reported

Thursday 11th October 2018

No incidents reported

Wednesday 10th October 2018

Version 5 Docker Daemon Restart

Today, we added localhost,127.0.0.1,::1 to any configured no_proxy settings to simplify the behaviour while using tools like curl to connect to local resources.

While this does not directly affect most services in production, Docker was restarted automatically by our automation software as a result of this change. Therefore, any Docker container running will be restarted between 13:00 and 14:00.

We only recognized this after it was already to late and apologize for this mistake. We will make sure that this will not happen again by adding this particular case to our test cases.