Seravo experienced a major incident on September 21, 2026 affecting fi-ellington cluster, lasting 3h 3m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Sep 21, 2026, 10:25 AM UTC
We identified a networking issue in cluster fi-ellington. Our team is working on it to fix it. We apologise for any inconvenience.
- monitoring Sep 21, 2026, 12:04 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 21, 2026, 01:29 PM UTC
This incident has been resolved.
- postmortem Sep 22, 2026, 10:05 AM UTC
# Notice of a cluster outage on September 21, 2026 On Monday, September 21, 2026, we suffered from a partial outage on our server cluster FI-Ellington. The problem began at 13:15 \(UTC\+3\) and was completely resolved at 16:29. However, most of the sites remained to function until 14:20. Some sites were still needed to restart manually. The problem was related to a database service overload, affecting most of the websites hosted in the FI-Ellington cluster. The repair operations were unfortunately time-taking. Once the database service was fixed, we still needed to restart some of the site instances manually. To improve our processes for such possible issues in the future, we have implemented new tools to recover website instances faster. In addition, we have improved Seravo’s 24/7 monitoring in order to recognize issues of this type sooner. We apologize for the downtime and inconvenience caused by this incident. 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\) * 13:15 The first site alerts, investigation was started * 13:20 The issue was identified and limited to the database system * 13:25 Issue was reported on status.seravo.com * 13:50 Recovery measures * 14:20 The most sites were recovered * 14:20 Failed sites were identified and instance restarts initiated * 16:29 All sites recovered