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.

  • libopenexr-3-1-30/stable-security 3.2.12-1~deb13u1 amd64 [upgradable from: 3.1.13-2]

Start maintenance window: 11/11/2026 23:00
Stop maintenance window: 12/11/2026 02:00

Update Zammad

We will update Zammad to version 7.2.3.

Reference: #103

Start maintenance window: 11/11/2026 23:00
Stop maintenance window: 12/11/2026 02:00

Matomo: Changes to Multi-Server Setups

To improve stability and maintainability of larger Dedicated Matomo installations, we will perform some planned changes to the configuration.

Why this change?

Operating Matomo in a multi-server setup contains some complexity. We will further standardize and optimize the structure of the single parts of the stack, the monitoring and our automation. This will ensure we can further improve stability and performance, while reducing operational overhead and improving maintainability.

Which installations are affected?

These planned changes affect larger Dedicated Matomo installations that we operate on multiple servers. We will perform the planned changes one installation after the other during this 2-day maintenance window.

What does this mean?

  • Tracking of website users will continue without interruption, no tracking-data will be lost.
  • Access to the Matomo GUI for accessing the statistics will be interrupted temporarily for a short period of approx. 30-60 minutes per installation.
  • After the Matomo GUI is accessible again, tracking-data of the current day will show up with a slight delay until the queued tracking-data backlog is processed (duration of this process depends on the amount of tracking-data to be processed from the queue).

You don't have to do or change anything regarding this change.

If you have any questions, do not hesitate to contact us.

Start maintenance window: 16/11/2026 08:00
Stop maintenance window: 17/11/2026 18:00

Mailcow: Changes to Email Alias Forwarding

To improve email deliverability, we will restrict email aliases from forwarding messages to external domains.

Why this change?

Forwarding emails to external providers can cause authentication issues (particularly SPF), resulting in messages being rejected or classified as spam.

What does this mean?

  • Existing aliases will continue to work as usual, unless modified.
  • Forwarding to locally hosted domains remains unaffected.
  • Creating or modifying aliases to forward to external domains will be restricted.
  • External forwarding will remain possible through an alternative method.

For instructions, please see our forwarding guide.

If you have any questions, do not hesitate to contact us.

Start maintenance window: 30/11/2026 23:00
Stop maintenance window: 01/12/2026 02:00

Past Incidents

Monday 6th July 2020

Mailserver Update, scheduled 6 years ago

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

With this update we disable TLS 1.0 and TLS 1.1. Please contact us if you have an old client, we can reactivate TLS 1.0 and TLS 1.1 if necessary. This change does not affect unauthenticated smtp via port 25.

Start maintenance window: 06/07/2020 23:00 MEZ
Stop maintenance window: 07/07/2020 01:00 MEZ

New features / Changes:

  • App passwords for imap and smtp
  • Reject documents with macros
  • Disabling TLS 1.0 and 1.1 for submission, smtp, imap and pop3
  • Show last mail login (pop3, imap)) in web interface
  • Read only API Key

Wednesday 24th June 2020

No incidents reported

Tuesday 23rd June 2020

No incidents reported

Monday 22nd June 2020

No incidents reported

Sunday 21st June 2020

No incidents reported

Saturday 20th June 2020

No incidents reported

Friday 19th June 2020

No incidents reported

Thursday 18th June 2020

Network DDoS Attack

Due to a ongoing DDoS attack, our network is only partially reachable. We are in process of eliminating the traffic in question.

Update 08:13: The traffic in question was identified and blocked, all services are reachable again. We will monitor the situation closely.

Update 09:14: Our mitigation measures proofed to be reliable.