Seravo Outage History

Seravo is up right now

There were 12 Seravo outages since February 3, 2026 totaling 25h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.seravo.com

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 →

Critical March 12, 2026

Availability issues in cluster fi-perko

Detected by Pingoru
Mar 12, 2026, 03:10 AM UTC
Resolved
Mar 12, 2026, 07:47 AM UTC
Duration
4h 36m
Affected: fi-perko cluster
Timeline · 5 updates
  1. investigating Mar 12, 2026, 03:10 AM UTC

    We are currently investigating this issue.

  2. identified Mar 12, 2026, 04:33 AM UTC

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

  3. monitoring Mar 12, 2026, 06:21 AM UTC

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

  4. resolved Mar 12, 2026, 07:47 AM UTC

    This incident has been resolved.

  5. postmortem Mar 13, 2026, 09:37 AM UTC

    # Notice of a Server Outage on March 12, 2026 On Thursday March 12, 2026, a failure related to the server resource usage caused an outage in the cluster fi-perko. The outage was caused by a newly implemented security feature which led to increased resource usage. Monitoring failed to notice and pinpoint the increased resource usage in time, which led to the outage. The outage was aggravated by an unrelated networking change which led to delay in recovery. This caused an outage to all sites in the fi-perko cluster. The problem was noticed immediately by our on-call monitoring processes, and measures were immediately implemented to begin recovery. The disruption first began at 04:00 \(UTC\+2\), escalated at 05:00 and ended at 08:19 \(UTC\+2\). We apologise for any inconvenience caused by the disruption. ## Timeline \(all timestamps UTC\+2 \(EET\)\) * 12.3.2026 03:47 Partial outage * 12.3.2026 03:52 On-call performs initial recovery measures * 12.3.2026 04:00 Recovered from partial outage * 12.3.2026 05:00 Incident escalated again * 12.3.2026 05:10 On-call attempts recovery measures * 12.3.2026 05:15 Full outage * 12.3.2026 05:27 On-call performs recovery measures * 12.3.2026 06:17 Recovered from the outage - begin site recovery * 12.3.2026 08:19 All affected sites were back online ## Follow-Up Action As a result of the incident, we at Seravo have identified the need for the following measures: * Testing new features with extended data-sets to be able to catch issues caused by the sheer volume of processed data * Improvements to system resource monitoring

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 →

Minor February 25, 2026

Availability issues with sites using external DNS

Detected by Pingoru
Feb 25, 2026, 09:14 PM UTC
Resolved
Feb 25, 2026, 09:19 PM UTC
Duration
4m
Affected: External Services
Timeline · 2 updates
  1. investigating Feb 25, 2026, 09:14 PM UTC

    Customers that have opted to use external DNS for their site might encounter availability issues with their sites. Incident does not affect customers using only Seravo-provided hosting services.

  2. resolved Feb 25, 2026, 09:19 PM UTC

    This incident has been resolved.

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 →

Looking to track Seravo downtime and outages?

Pingoru polls Seravo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Seravo reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Seravo alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Seravo for free

5 free monitors · No credit card required