Seravo Outage History

Seravo is up right now

Seravo had 35 outages in the last 2 years totaling 10h 15m of downtime — averaging 1.4 incidents per month.

There were 35 Seravo outages since June 25, 2025 totaling 10h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.seravo.com

Minor December 2, 2025

Database issue in cluster fi-lahti

Detected by Pingoru
Dec 02, 2025, 07:18 PM UTC
Resolved
Dec 02, 2025, 07:35 PM UTC
Duration
16m
Affected: fi-lahti cluster
Timeline · 2 updates
  1. investigating Dec 02, 2025, 07:18 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 02, 2025, 07:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 30, 2025

Networking issue in cluster de-dauner

Detected by Pingoru
Nov 30, 2025, 02:19 PM UTC
Resolved
Nov 30, 2025, 05:20 PM UTC
Duration
3h 1m
Affected: de-dauner cluster
Timeline · 3 updates
  1. identified Nov 30, 2025, 02:19 PM UTC

    We identified a networking issue in cluster. Our team is working on it to fix it. We apologise for any inconvenience.

  2. monitoring Nov 30, 2025, 03:24 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 30, 2025, 05:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 28, 2025

Network issue in cluster fi-perko

Detected by Pingoru
Nov 28, 2025, 12:28 PM UTC
Resolved
Nov 28, 2025, 01:16 PM UTC
Duration
48m
Affected: fi-perko cluster
Timeline · 3 updates
  1. investigating Nov 28, 2025, 12:28 PM UTC

    We identified a networking issue in cluster fi-perko. Our team is working on it to fix it. We apologise for any inconvenience.

  2. monitoring Nov 28, 2025, 01:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 28, 2025, 01:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 6, 2025

Networking issue in cluster fi-haarla

Detected by Pingoru
Nov 06, 2025, 12:00 PM UTC
Resolved
Nov 06, 2025, 12:25 PM UTC
Duration
25m
Affected: fi-haarla cluster
Timeline · 3 updates
  1. identified Nov 06, 2025, 12:00 PM UTC

    We identified a networking issue in cluster fi-haarla. Our team is working on it to fix it. We apologise for any inconvenience.

  2. monitoring Nov 06, 2025, 12:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 06, 2025, 12:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 4, 2025

Networking issue in cluster fi-coltrane

Detected by Pingoru
Nov 04, 2025, 07:11 PM UTC
Resolved
Nov 04, 2025, 07:29 PM UTC
Duration
18m
Affected: fi-coltrane cluster
Timeline · 3 updates
  1. identified Nov 04, 2025, 07:11 PM UTC

    We identified a networking issue in cluster fi-coltrane. Our team is working on it to fix it. We apologise for any inconvenience.

  2. monitoring Nov 04, 2025, 07:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Nov 04, 2025, 07:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 29, 2025

Database issue in cluster fi-ellington

Detected by Pingoru
Sep 29, 2025, 10:34 AM UTC
Resolved
Sep 29, 2025, 11:29 AM UTC
Duration
55m
Affected: fi-ellington cluster
Timeline · 3 updates
  1. investigating Sep 29, 2025, 10:34 AM UTC

    We have noticed database connectivity problems in cluster fi-ellington. We are investigating the issue.

  2. monitoring Sep 29, 2025, 10:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 29, 2025, 11:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 16, 2025

Networking issue in cluster fi-rantala

Detected by Pingoru
Sep 16, 2025, 02:40 PM UTC
Resolved
Sep 16, 2025, 05:25 PM UTC
Duration
2h 45m
Affected: fi-rantala cluster
Timeline · 3 updates
  1. identified Sep 16, 2025, 02:40 PM UTC

    We identified a networking issue in cluster fi-rantala. Our team is working on it to fix it. We apologise for any inconvenience.

  2. monitoring Sep 16, 2025, 02:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 16, 2025, 05:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 12, 2025

Database issue in cluster fi-haarla

Detected by Pingoru
Sep 12, 2025, 04:28 PM UTC
Resolved
Sep 12, 2025, 05:24 PM UTC
Duration
55m
Affected: fi-haarla cluster
Timeline · 4 updates
  1. investigating Sep 12, 2025, 04:28 PM UTC

    We have noticed database connectivity problems in cluster fi-haarla. We are investigating the issue.

  2. monitoring Sep 12, 2025, 04:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. investigating Sep 12, 2025, 04:58 PM UTC

    We have noticed database connectivity problems in cluster fi-haarla. We are investigating the issue.

  4. resolved Sep 12, 2025, 05:24 PM UTC

    This incident has been resolved.

Read the full incident report →

Major August 27, 2025

Database issue in cluster fi-fredriksson

Detected by Pingoru
Aug 27, 2025, 06:28 AM UTC
Resolved
Aug 27, 2025, 06:48 AM UTC
Duration
20m
Affected: fi-fredriksson cluster
Timeline · 3 updates
  1. investigating Aug 27, 2025, 06:28 AM UTC

    We have noticed database connectivity problems in cluster fi-fredriksson. We are investigating the issue.

  2. monitoring Aug 27, 2025, 06:33 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 27, 2025, 06:48 AM UTC

    This incident has been resolved.

Read the full incident report →