Seravo status history
Current state: operational — “All Systems Operational” per https://status.seravo.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Seravo incidents last?
From 53 incidents with a vendor-posted start and resolve time. Longest on record: Delays in WordPress site emails sent to Outlook / Office 365 — 18.8 h (2026-09-04 11:58 UTC). Excluded, never estimated: 1 scheduled maintenance. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (54)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-10 06:00 UTC | Customer Support Phone Line not available | maintenance | maintenance | 2 d 6 h (approx.) |
| 2026-09-09 06:24 UTC | Database issue in cluster fi-sestak | resolved | major | 25 min |
| 2026-09-07 08:35 UTC | Database issues in cluster FI-Metheny | resolved | minor | 1 h 06 min |
| 2026-09-04 11:58 UTC | Delays in WordPress site emails sent to Outlook / Office 365 | resolved | minor | 18 h 50 min |
| 2026-08-11 11:11 UTC | Availability issues in cluster fi-fredriksson | resolved | minor | 14 min |
| 2026-07-21 10:12 UTC | Availability issues in cluster fi-fredriksson | resolved | major | 2 h 12 min |
| 2026-06-27 18:42 UTC | Networking issue in cluster de-dauner | resolved | critical | 1 h 21 min |
| 2026-06-26 20:53 UTC | Availability issues in cluster fi-rantala | resolved | major | 57 min |
| 2026-06-25 18:19 UTC | Networking issue in cluster fi-metheny | resolved | major | 1 h 00 min |
| 2026-06-17 07:06 UTC | Database issue in cluster fi-tolonen | resolved | major | 30 min |
| 2026-06-15 13:36 UTC | Availability issues with sites using external DNS | resolved | critical | 5 h 49 min |
| 2026-06-10 04:30 UTC | Availability issues in fi-haarla | resolved | minor | 11 min |
| 2026-06-09 03:25 UTC | Networking issue in clusters | postmortem | major | 58 min |
| 2026-05-05 21:39 UTC | External DNS issues on .de domains | resolved | minor | 6 h 21 min |
| 2026-04-22 11:08 UTC | Networking issue in cluster fi-sestak | resolved | major | 44 min |
| 2026-03-31 00:13 UTC | Networking issue in cluster fi-sestak | resolved | major | 29 min |
| 2026-03-25 11:22 UTC | Networking issue in cluster us-davis | resolved | major | 18 min |
| 2026-03-24 06:14 UTC | Networking issue in cluster fi-sestak | resolved | minor | 1 h 08 min |
| 2026-03-12 15:45 UTC | Availability issues in cluster FI-Fredriksson | resolved | major | 33 min |
| 2026-03-12 03:10 UTC | Availability issues in cluster fi-perko | postmortem | critical | 4 h 36 min |
| 2026-03-12 01:56 UTC | Availability issues in cluster fi-perko | resolved | critical | 38 min |
| 2026-03-11 05:19 UTC | Availability issues in cluster fi-fredriksson | resolved | major | 1 h 32 min |
| 2026-03-05 15:08 UTC | Third party API failures causing site issues | resolved | minor | 3 h 50 min |
| 2026-02-25 21:14 UTC | Availability issues with sites using external DNS | resolved | minor | 4 min |
| 2026-02-25 21:00 UTC | Networking issue in multiple clusters | resolved | none | 0 min |
| 2026-02-17 14:06 UTC | Availability issues in us-davis cluster | resolved | major | 4 min |
| 2026-02-06 13:18 UTC | Networking issues in cluster fi-coltrane | resolved | minor | 3 h 04 min |
| 2026-02-06 06:23 UTC | Active DDoS campaign | resolved | minor | 9 h 23 min |
| 2026-02-03 13:13 UTC | Networking issues in cluster us-davis | resolved | major | 47 min |
| 2026-01-30 10:18 UTC | Networking issue in cluster fi-perko | resolved | major | 29 min |
| 2026-01-30 06:59 UTC | Networking issue in cluster fi-perko | resolved | minor | 2 h 31 min |
| 2026-01-29 20:01 UTC | Database issue in fi-ellington | resolved | minor | 19 min |
| 2026-01-29 07:43 UTC | Availability issues in cluster fi-ellington | resolved | minor | 45 min |
| 2026-01-28 05:28 UTC | Availability issues in multiple clusters | postmortem | major | 4 h 38 min |
| 2026-01-23 03:46 UTC | Availability issues in cluster fi-perko | resolved | major | 19 min |
| 2026-01-19 05:36 UTC | Networking issue in cluster fi-fredriksson | resolved | major | 34 min |
| 2026-01-16 20:30 UTC | Availability issues in cluster fi-ellington | resolved | major | 13 h 56 min |
| 2025-12-19 05:14 UTC | Availability issues in cluster fi-fredriksson | resolved | minor | 56 min |
| 2025-12-15 07:28 UTC | Availability issues in cluster se-broo | resolved | major | 1 h 09 min |
| 2025-12-09 01:14 UTC | Networking issue in cluster fi-fredriksson | resolved | major | 38 min |
| 2025-12-07 09:41 UTC | Availability issues in cluster us-davis | resolved | none | 49 min |
| 2025-12-05 08:58 UTC | Clouldflare related availability issues | resolved | minor | 57 min |
| 2025-12-03 16:49 UTC | Networking issue in cluster fi-ellington | resolved | none | 13 min |
| 2025-12-02 19:18 UTC | Database issue in cluster fi-lahti | resolved | minor | 16 min |
| 2025-11-30 14:19 UTC | Networking issue in cluster de-dauner | resolved | minor | 3 h 01 min |
| 2025-11-28 12:28 UTC | Network issue in cluster fi-perko | resolved | minor | 48 min |
| 2025-11-18 11:45 UTC | Clouldflare related availability issues | resolved | minor | 6 h 48 min |
| 2025-11-06 12:00 UTC | Networking issue in cluster fi-haarla | resolved | major | 25 min |
| 2025-11-04 19:11 UTC | Networking issue in cluster fi-coltrane | resolved | major | 18 min |
| 2025-11-04 12:29 UTC | Networking issue in cluster fi-fredriksson | resolved | minor | 59 min |
| 2025-10-19 00:17 UTC | Networking issue in cluster fi-fredriksson | resolved | major | 16 min |
| 2025-10-13 13:15 UTC | Networking issue in cluster fi-sestak | resolved | major | 59 min |
| 2025-10-06 12:02 UTC | Database issue in cluster fi-tolonen | resolved | major | 13 min |
| 2025-09-29 10:34 UTC | Database issue in cluster fi-ellington | resolved | minor | 55 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Seravo with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"seravo"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}