Seravo Outage History

Seravo is up right now

Pingoru has recorded 56 incidents for Seravo: 54 in the last 12 months and 9 in the last 90 days.

Source: status.seravo.com

56incidents recorded
54last 12 months
9last 90 days
3 hourstypical duration
Incidents per month
048AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct13%
Pingoru began tracking Seravo in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202611 of 720 (0%)
May 202616 of 744 (1%)
June 2026711 of 720 (2%)
July 202612 of 744 (0%)
August 202610 of 744 (0%)
September 2026524 of 720 (3%)
October 2026374 of 588 (13%)

Incidents, newest first

Major January 30, 2026 Networking issue in cluster fi-perko 29m fi-perko cluster

Started Jan 30, 2026, 10:18 AM UTC· resolved Jan 30, 2026, 10:47 AM UTC

  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 19m fi-ellington cluster

Started Jan 29, 2026, 08:01 PM UTC· resolved Jan 29, 2026, 08:21 PM UTC

  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 45m fi-ellington cluster

Started Jan 29, 2026, 07:43 AM UTC· resolved Jan 29, 2026, 08:28 AM UTC

  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 4h 38m fi-coltrane cluster, fi-ellington cluster, fi-haarla cluster, fi-metheny cluster and 6 more

Started Jan 28, 2026, 05:28 AM UTC· resolved Jan 28, 2026, 10:07 AM UTC

  1. identified Jan 28, 2026, 05:28 AM UTC

    Theres an availability issues in multiple clusters which affect small amount of sites. We have identified the problem and working on a solution at the moment.

  2. identified Jan 28, 2026, 06:57 AM UTC

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

  3. monitoring Jan 28, 2026, 08:57 AM UTC

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

  4. resolved Jan 28, 2026, 10:07 AM UTC

    This incident has been resolved.

  5. postmortem Jan 30, 2026, 01:03 PM UTC

    # Notice of a Service Disruption on January 28, 2026 On Wednesday January 28, 2026, a failure related to the Nginx web server occurred in several Seravo server clusters. The disruption was caused by an improvement on our security features and a minor change in Nginx configurations. This caused an outage to a number of sites in the clusters. The problem was noticed immediately by our on-call monitoring processes, and was fixed as quickly as possible.Technical complications during the roll-back delayed the full restoration of site services. The disruption began at 07:00 \(UTC\+2\) and ended at 10:00. We apologise for any inconvenience caused by the disruption. ## Timeline \(all timestamps UTC\+2 \(EET\) * 28.1.2026 07:00 Nginx misconfiguration was rolled-out * 28.1.2026 07:06 Site monitoring noticed site issues and alerted on-call officer * 28.1.2026 07:10 Investigation was started * 28.1.2026 07:21 The root cause was identified * 28.1.2026 07:21 Problem was escalated to the systems administration team * 28.1.2026 07:34 The team started fixing the issue * 28.1.2026 07:49 Some of the sites were recovered * 28.1.2026 09:06 Almost the whole cluster was fixed * 28.1.2026 10:00 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: * Further development of internal processes and tools to enable faster troubleshooting and recovery. * Improvements to automated testing for configuration changes.

Read the full incident report →

Major January 19, 2026 Networking issue in cluster fi-fredriksson 34m fi-fredriksson cluster

Started Jan 19, 2026, 05:36 AM UTC· resolved Jan 19, 2026, 06:10 AM UTC

  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 1h 9m se-broo cluster

Started Dec 15, 2025, 07:28 AM UTC· resolved Dec 15, 2025, 08:37 AM UTC

  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 49m us-davis cluster

Started Dec 07, 2025, 09:41 AM UTC· resolved Dec 07, 2025, 10:30 AM UTC

  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 57m External Services

Started Dec 05, 2025, 08:58 AM UTC· resolved Dec 05, 2025, 09:55 AM UTC

  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 →

Minor December 2, 2025 Database issue in cluster fi-lahti 16m fi-lahti cluster

Started Dec 02, 2025, 07:18 PM UTC· resolved Dec 02, 2025, 07:35 PM UTC

  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 28, 2025 Network issue in cluster fi-perko 48m fi-perko cluster

Started Nov 28, 2025, 12:28 PM UTC· resolved Nov 28, 2025, 01:16 PM UTC

  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 25m fi-haarla cluster

Started Nov 06, 2025, 12:00 PM UTC· resolved Nov 06, 2025, 12:25 PM UTC

  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 18m fi-coltrane cluster

Started Nov 04, 2025, 07:11 PM UTC· resolved Nov 04, 2025, 07:29 PM UTC

  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 →