Seravo Outage History

Seravo is up right now

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

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

Source: https://status.seravo.com

Major June 17, 2026

Database issue in cluster fi-tolonen

Detected by Pingoru
Jun 17, 2026, 07:06 AM UTC
Resolved
Jun 17, 2026, 07:36 AM UTC
Duration
30m
Affected: fi-tolonen cluster
Timeline · 3 updates
  1. investigating Jun 17, 2026, 07:06 AM UTC

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

  2. identified Jun 17, 2026, 07:09 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Jun 17, 2026, 07:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 15, 2026

Availability issues with sites using external DNS

Detected by Pingoru
Jun 15, 2026, 01:36 PM UTC
Resolved
Jun 15, 2026, 07:25 PM UTC
Duration
5h 49m
Affected: External Services
Timeline · 2 updates
  1. monitoring Jun 15, 2026, 01:36 PM UTC

    Customers that have opted to use external DNS ( dns{1..4}triuvare-webhosting.fi) for their site might encounter availability issues with their sites. Incident does not affect customers using only Seravo-provided hosting services.

  2. resolved Jun 15, 2026, 07:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 10, 2026

Availability issues in fi-haarla

Detected by Pingoru
Jun 10, 2026, 04:30 AM UTC
Resolved
Jun 10, 2026, 04:41 AM UTC
Duration
11m
Affected: fi-haarla cluster
Timeline · 3 updates
  1. identified Jun 10, 2026, 04:30 AM UTC

    We are experiencing availability issues in cluster fi-haarla. Some websites may experience interruptions. Our team is actively investigating and resolving the situation. We apologise for any inconvenience. Thank you for your patience.

  2. monitoring Jun 10, 2026, 04:36 AM UTC

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

  3. resolved Jun 10, 2026, 04:41 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 9, 2026

Networking issue in clusters

Detected by Pingoru
Jun 09, 2026, 03:25 AM UTC
Resolved
Jun 09, 2026, 04:24 AM UTC
Duration
58m
Affected: fi-coltrane clusterfi-ellington clusterfi-haarla clusterfi-metheny clusterfi-perko clusterfi-rantala clusterfi-sestak clusterfi-tolonen clusterfi-lahti clusterfi-fredriksson cluster
Timeline · 5 updates

Read the full incident report →

Minor May 5, 2026

External DNS issues on .de domains

Detected by Pingoru
May 05, 2026, 09:39 PM UTC
Resolved
May 06, 2026, 04:01 AM UTC
Duration
6h 21m
Affected: de-dauner cluster
Timeline · 2 updates
  1. investigating May 05, 2026, 09:39 PM UTC

    Due to a fault, there is currently limited availability to the recursive DNS resolution for "de" domains. This might affect some of our customers. More info here: https://status.hetzner.com/incident/c5e4ec2e-82b5-4f1a-a7ce-37127a6f2aa9

  2. resolved May 06, 2026, 04:01 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 22, 2026

Networking issue in cluster fi-sestak

Detected by Pingoru
Apr 22, 2026, 11:08 AM UTC
Resolved
Apr 22, 2026, 11:52 AM UTC
Duration
44m
Affected: fi-sestak cluster
Timeline · 3 updates
  1. identified Apr 22, 2026, 11:08 AM UTC

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

  2. monitoring Apr 22, 2026, 11:40 AM UTC

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

  3. resolved Apr 22, 2026, 11:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 25, 2026

Networking issue in cluster us-davis

Detected by Pingoru
Mar 25, 2026, 11:22 AM UTC
Resolved
Mar 25, 2026, 11:40 AM UTC
Duration
18m
Affected: us-davis cluster
Timeline · 3 updates
  1. identified Mar 25, 2026, 11:22 AM UTC

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

  2. monitoring Mar 25, 2026, 11:25 AM UTC

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

  3. resolved Mar 25, 2026, 11:40 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 12, 2026

Availability issues in cluster FI-Fredriksson

Detected by Pingoru
Mar 12, 2026, 03:45 PM UTC
Resolved
Mar 12, 2026, 04:18 PM UTC
Duration
33m
Affected: fi-fredriksson cluster
Timeline · 2 updates
  1. investigating Mar 12, 2026, 03:45 PM UTC

    We are currently investigating this issue.

  2. resolved Mar 12, 2026, 04:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 11, 2026

Availability issues in cluster fi-fredriksson

Detected by Pingoru
Mar 11, 2026, 05:19 AM UTC
Resolved
Mar 11, 2026, 06:52 AM UTC
Duration
1h 32m
Affected: fi-fredriksson cluster
Timeline · 3 updates
  1. investigating Mar 11, 2026, 05:19 AM UTC

    We are currently investigating this issue.

  2. monitoring Mar 11, 2026, 05:47 AM UTC

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

  3. resolved Mar 11, 2026, 06:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 5, 2026

Third party API failures causing site issues

Detected by Pingoru
Mar 05, 2026, 03:08 PM UTC
Resolved
Mar 05, 2026, 06:59 PM UTC
Duration
3h 50m
Affected: fi-coltrane clusterfi-ellington clusterfi-haarla clusterfi-perko clusterfi-rantala clusterfi-sestak clusterfi-tolonen clusterfi-lahti clusterfi-fredriksson cluster
Timeline · 5 updates
  1. identified Mar 05, 2026, 03:08 PM UTC

    We identified an upstream service provider networking issue causing slowness on some sites. We apologise for any inconvenience.

  2. identified Mar 05, 2026, 04:01 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Mar 05, 2026, 04:24 PM UTC

    The problem is related to Meta API services that slow down the sites. The sites will remain to work normally after the issue is fixed by the service provider.

  4. monitoring Mar 05, 2026, 05:36 PM UTC

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

  5. resolved Mar 05, 2026, 06:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 5, 2026

Networking issue in multiple clusters

Detected by Pingoru
Mar 05, 2026, 09:56 AM UTC
Resolved
Feb 25, 2026, 09:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 05, 2026, 09:56 AM UTC

    On February 25 between 23:04–23:11, a short networking incident affected a portion of our customers. The disruption was caused by an issue at our data center provider related to an ongoing cyberattack. Due to the short duration and nature of the incident, it was not immediately reflected on our status page. https://status.hetzner.com/incident/5e901309-0873-42af-90c5-84f38304f592

Read the full incident report →

Major February 17, 2026

Availability issues in us-davis cluster

Detected by Pingoru
Feb 17, 2026, 02:06 PM UTC
Resolved
Feb 17, 2026, 02:11 PM UTC
Duration
4m
Affected: us-davis cluster
Timeline · 2 updates
  1. identified Feb 17, 2026, 02:06 PM UTC

    We are experiencing availability issues. Our team is actively investigating and resolving the situation. We apologise for any inconvenience. Thank you for your patience.

  2. resolved Feb 17, 2026, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 6, 2026

Networking issues in cluster fi-coltrane

Detected by Pingoru
Feb 06, 2026, 01:18 PM UTC
Resolved
Feb 06, 2026, 04:23 PM UTC
Duration
3h 4m
Affected: fi-coltrane cluster
Timeline · 2 updates
  1. investigating Feb 06, 2026, 01:18 PM UTC

    We are currently investigating this issue.

  2. resolved Feb 06, 2026, 04:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 6, 2026

Active DDoS campaign

Detected by Pingoru
Feb 06, 2026, 06:23 AM UTC
Resolved
Feb 06, 2026, 03:46 PM UTC
Duration
9h 23m
Affected: fi-fredriksson cluster
Timeline · 3 updates
  1. identified Feb 06, 2026, 06:23 AM UTC

    We are under an active DDoS campaign and we are mitigating the issue. All the data is safe. If the campaign is related to a specific domain or web site, we are in contact with the customer in question separately.

  2. monitoring Feb 06, 2026, 09:58 AM UTC

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

  3. resolved Feb 06, 2026, 03:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 3, 2026

Networking issues in cluster us-davis

Detected by Pingoru
Feb 03, 2026, 01:13 PM UTC
Resolved
Feb 03, 2026, 02:01 PM UTC
Duration
47m
Affected: us-davis cluster
Timeline · 3 updates
  1. investigating Feb 03, 2026, 01:13 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 03, 2026, 01:55 PM UTC

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

  3. resolved Feb 03, 2026, 02:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 30, 2026

Networking issue in cluster fi-perko

Detected by Pingoru
Jan 30, 2026, 10:18 AM UTC
Resolved
Jan 30, 2026, 10:47 AM UTC
Duration
29m
Affected: fi-perko cluster
Timeline · 3 updates
  1. identified Jan 30, 2026, 10:18 AM 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 Jan 30, 2026, 10:21 AM UTC

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

  3. resolved Jan 30, 2026, 10:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

Database issue in fi-ellington

Detected by Pingoru
Jan 29, 2026, 08:01 PM UTC
Resolved
Jan 29, 2026, 08:21 PM UTC
Duration
19m
Affected: fi-ellington cluster
Timeline · 3 updates
  1. investigating Jan 29, 2026, 08:01 PM UTC

    We are currently investigating this issue.

  2. monitoring Jan 29, 2026, 08:03 PM UTC

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

  3. resolved Jan 29, 2026, 08:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 29, 2026

Availability issues in cluster fi-ellington

Detected by Pingoru
Jan 29, 2026, 07:43 AM UTC
Resolved
Jan 29, 2026, 08:28 AM UTC
Duration
45m
Affected: fi-ellington cluster
Timeline · 3 updates
  1. investigating Jan 29, 2026, 07:43 AM UTC

    We are experiencing availability issues in cluster fi-ellington. Our team is actively investigating and resolving the situation. We apologise for any inconvenience. Thank you for your patience.

  2. monitoring Jan 29, 2026, 07:51 AM UTC

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

  3. resolved Jan 29, 2026, 08:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 28, 2026

Availability issues in multiple clusters

Detected by Pingoru
Jan 28, 2026, 05:28 AM UTC
Resolved
Jan 28, 2026, 10:07 AM UTC
Duration
4h 38m
Affected: fi-coltrane clusterfi-ellington clusterfi-haarla clusterfi-metheny clusterfi-perko clusterfi-rantala clusterfi-sestak clusterfi-tolonen clusterfi-lahti clusterfi-fredriksson cluster
Timeline · 5 updates

Read the full incident report →

Major January 19, 2026

Networking issue in cluster fi-fredriksson

Detected by Pingoru
Jan 19, 2026, 05:36 AM UTC
Resolved
Jan 19, 2026, 06:10 AM UTC
Duration
34m
Affected: fi-fredriksson cluster
Timeline · 3 updates
  1. identified Jan 19, 2026, 05:36 AM UTC

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

  2. monitoring Jan 19, 2026, 05:45 AM UTC

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

  3. resolved Jan 19, 2026, 06:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 15, 2025

Availability issues in cluster se-broo

Detected by Pingoru
Dec 15, 2025, 07:28 AM UTC
Resolved
Dec 15, 2025, 08:37 AM UTC
Duration
1h 9m
Affected: se-broo cluster
Timeline · 3 updates
  1. investigating Dec 15, 2025, 07:28 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 15, 2025, 08:00 AM UTC

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

  3. resolved Dec 15, 2025, 08:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 7, 2025

Availability issues in cluster us-davis

Detected by Pingoru
Dec 07, 2025, 09:41 AM UTC
Resolved
Dec 07, 2025, 10:30 AM UTC
Duration
49m
Affected: us-davis cluster
Timeline · 3 updates
  1. investigating Dec 07, 2025, 09:41 AM UTC

    We are currently investigating this issue.

  2. identified Dec 07, 2025, 09:50 AM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Dec 07, 2025, 10:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 5, 2025

Clouldflare related availability issues

Detected by Pingoru
Dec 05, 2025, 08:58 AM UTC
Resolved
Dec 05, 2025, 09:55 AM UTC
Duration
57m
Affected: External Services
Timeline · 3 updates
  1. identified Dec 05, 2025, 08:58 AM UTC

    Some sites using Cloudflare are experiencing issues and have degraded availability. We're investigating further, but issue seems to be external.

  2. monitoring Dec 05, 2025, 09:17 AM UTC

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

  3. resolved Dec 05, 2025, 09:55 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 3, 2025

Networking issue in cluster fi-ellington

Detected by Pingoru
Dec 03, 2025, 04:49 PM UTC
Resolved
Dec 03, 2025, 05:02 PM UTC
Duration
13m
Affected: fi-ellington cluster
Timeline · 2 updates
  1. investigating Dec 03, 2025, 04:49 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 03, 2025, 05:02 PM UTC

    This incident has been resolved.

Read the full incident report →