Statusfield LogoStatusfield
Seravo status
Seravo logo and current status indicator

Seravo Incident History

Operational

seravo.com ↗11 top-level components

checked Oct 27, 2026 11:15 AM UTC · Seravo's official status page

Seravo is up and running.

Seravo is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches Seravo alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Seravo incident history

4 reports published by Seravo in the last 30 days · 1 still open

When Seravo breaks, it is typically resolved in 4h 4m — median across 1 resolved incidents over 30 days.

October 23, 2026

PHP Vulnerability (CVE-2026-115560)

Ongoing · last update

  1. identifiedOct 23 · 11:39 UTC

    PHP Foundation has announced yet another vulnerability in PHP interpreter, tracked as CVE-2026-115560, see announcement at https://www.php.net/archive/2026.php#2026-10-23-1 . This vulnerability, unlike the previous one, will need special configuration to be exploited, so any real-world attack against our customers is unlikely using this vulnerability. Seravo will mitigate and apply patches on behalf of all customers when patch is made available.

Reported by Seravo on their status page.

October 21, 2026

Critical PHP vulnerabilities

Last update

  1. resolvedOct 22 · 05:48 UTC

    This incident has been resolved.

Reported by Seravo on their status page.

October 6, 2026

Availability issues in cluster fi-haarla

Last update

  1. postmortemOct 7 · 12:11 UTC

    DDoS attack at FI-Haarla

    On Tuesday, October 6, 2026, Seravo's server cluster FI-Haarla became a target of a large-scale DDoS attack. DDoS stands for Distributed Denial of Service, a malicious cyberattack that floods a server with overwhelming internet traffic to make it unresponsive and stop working for real users.

    The attack started at 9:00 (UTC+3). During the attack most of the websites hosted in FI-Haarla experienced degraded service, but there was no other security threat to the sites. Visitors saw connection timeouts or HTTP502 errors when trying to visit the sites. The affected parties and relevant authorities have been informed, and no customer action is required.

    As part of our response, we encountered difficulties deploying the tools needed to mitigate the attack. We’ll review and improve our process to help prevent similar issues in future incidents.

    The attack ended at approximately 10:47, after which we continued to monitor the situation. The incident was marked as resolved on our end at 12:49.

    We apologize for the inconvenience caused by this attack.

    Seravo provides real-time updates on all disruptions at status.seravo.com. We highly recommend subscribing to incident notifications via email, for example.

    Timeline (UTC+3)

    • 09:00 DDoS starts
    • 09:02 DDoS detected, response initiated
    • 09:10 Blocks implemented
    • 09:31 More actions taken to mitigate the attack traffic
    • 10:00 Issue encountered in tooling, fixes implemented
    • 10:26 Tooling proves not to have the desired effect
    • 10:33 Further action to mitigate the attack
    • 10:47 Traffic suppressed, sites start recovering from DDoS

Reported by Seravo on their status page.

September 21, 2026

Networking issue in cluster fi-sestak

Last update

  1. postmortemSep 22 · 10:06 UTC

    DDoS attack at FI-Sestak

    On Monday, September 21, 2026, Seravo's server cluster FI-Sestak became a target of a large-scale DDoS attack. DDoS stands for Distributed Denial of Service, a malicious cyberattack that floods a server with overwhelming internet traffic to make it unresponsive and stop working for real users.

    ‌

    The attack started at 12:45 (UTC+3). During the attack most of the websites hosted in FI-Sestak experienced degraded service, but there was no other security threat to the sites. Visitors received connection timeouts or HTTP502 errors while trying to visit the sites.

    ‌

    At approximately 13:15, an incident occurred in another cluster, FI-Ellington, initially raising concerns that the incident might be related to the DDoS attack in FI-Sestak. No indication of a connection between the two incidents was found. However, the overlap temporarily diverted attention and delayed recovery of FI-Sestak.

    ‌

    As a part of our response, we deployed new tooling to assist with mitigating an attack like this in the future. The tooling proved useful during the incident and will be retained in our toolkit for similar incidents in future.

    ‌

    The attack ended at approximately 14:20, after which we continued to monitor the situation. The incident was marked as resolved on our end at 15:03.

    ‌

    We apologize for the inconvenience caused by this attack.

    ‌

    Seravo provides real-time updates on all disruptions at status.seravo.com. We highly recommend subscribing to incident notifications via email, for example.

    Timeline (UTC+3)

    • 12:45 DDoS starts
    • 12:49 First signs of abnormal web traffic
    • 12:55 First blocks deployed to mitigate the attack
    • 13:15 A simultaneous, unrelated issue in another server cluster slows down investigation
    • 13:45 New tooling deployed
    • 14:08 New tooling proves effective
    • 14:20 DDoS ends
    • 15:03 Incident marked as resolved

Reported by Seravo on their status page.