Scheduled maintenance on multiple clusters.

Scheduled Maintenance Report for Seravo

Postmortem

Notice of a Service Disruption on December 19, 2025

On Friday December 19, 2025, Seravo's server cluster fi-ellington experienced a network failure during a scheduled maintenance, affecting almost all sites on the cluster. The disruption was caused by a configuration failure within the cluster’s internal network connections and was noticed immediately and was fixed as quickly as it was possible. However, due to a software error, our recovery processes did not work as expected, causing a longer downtime of some sites in the cluster.

The disruption began at 6:09 (UTC+2) and ended at 7:49. Most of the sites in the server cluster were accessible again at 6:50.

We apologise for any inconvenience caused by the disruption.

Timeline (all timestamps UTC+2 (EET)

  • 19.12.2025 6:09 Scheduled maintenance started.
  • 19.12.2025 6:12 Problem detection: Several sites reported problems.
  • 19.12.2025 6:12 Troubleshooting: Identified problem, started fixes
  • 19.12.2025 6:50 At this point most of the sites recovered.
  • 19.12.2025 7:04 Troubleshooting: Some sites still not yet recovered.
  • 19.12.2025 7:49 Recovery: All sites operational.

Follow-Up Action

As a result of the incident, we at Seravo have identified the need for the following improvements:

  • Further development of internal processes and tools to enable faster troubleshooting and recovering.
  • Improvements to communication processes during an active service disruption.
Posted Dec 22, 2025 - 08:45 UTC

Completed

The scheduled maintenance has been completed.
Posted Dec 19, 2025 - 06:00 UTC

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Dec 19, 2025 - 04:00 UTC

Scheduled

We will be undergoing scheduled maintenance during this time.

This might cause short interruptions with the sites located in those clusters. We apologize for possible inconvenience.
Posted Dec 16, 2025 - 12:05 UTC
This scheduled maintenance affected: Germany (de-dauner cluster), Finland (fi-ellington cluster, fi-haarla cluster, fi-metheny cluster, fi-perko cluster, fi-rantala cluster, fi-sestak cluster, fi-tolonen cluster, fi-lahti cluster), and Sweden (se-abba cluster).