Vendor Status Watch

← all vendors

Seravo status history

Current state: operational — “All Systems Operational” per https://status.seravo.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

4incidents, last 30 days
9incidents, last 90 days
54incidents on record
Incidents per week, last 12 weeks:

How long do Seravo incidents last?

49 minmedian incident duration53 measured
5.8 h90th percentile1 in 10 ran longer
38 minmedian, major/critical only29 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-10 06:00 UTCCustomer Support Phone Line not availablemaintenancemaintenance2 d 6 h (approx.)
2026-09-09 06:24 UTCDatabase issue in cluster fi-sestakresolvedmajor25 min
2026-09-07 08:35 UTCDatabase issues in cluster FI-Methenyresolvedminor1 h 06 min
2026-09-04 11:58 UTCDelays in WordPress site emails sent to Outlook / Office 365resolvedminor18 h 50 min
2026-08-11 11:11 UTCAvailability issues in cluster fi-fredrikssonresolvedminor14 min
2026-07-21 10:12 UTCAvailability issues in cluster fi-fredrikssonresolvedmajor2 h 12 min
2026-06-27 18:42 UTCNetworking issue in cluster de-daunerresolvedcritical1 h 21 min
2026-06-26 20:53 UTCAvailability issues in cluster fi-rantalaresolvedmajor57 min
2026-06-25 18:19 UTCNetworking issue in cluster fi-methenyresolvedmajor1 h 00 min
2026-06-17 07:06 UTCDatabase issue in cluster fi-tolonenresolvedmajor30 min
2026-06-15 13:36 UTCAvailability issues with sites using external DNSresolvedcritical5 h 49 min
2026-06-10 04:30 UTCAvailability issues in fi-haarlaresolvedminor11 min
2026-06-09 03:25 UTCNetworking issue in clusterspostmortemmajor58 min
2026-05-05 21:39 UTCExternal DNS issues on .de domainsresolvedminor6 h 21 min
2026-04-22 11:08 UTCNetworking issue in cluster fi-sestakresolvedmajor44 min
2026-03-31 00:13 UTCNetworking issue in cluster fi-sestakresolvedmajor29 min
2026-03-25 11:22 UTCNetworking issue in cluster us-davisresolvedmajor18 min
2026-03-24 06:14 UTCNetworking issue in cluster fi-sestakresolvedminor1 h 08 min
2026-03-12 15:45 UTCAvailability issues in cluster FI-Fredrikssonresolvedmajor33 min
2026-03-12 03:10 UTCAvailability issues in cluster fi-perkopostmortemcritical4 h 36 min
2026-03-12 01:56 UTCAvailability issues in cluster fi-perkoresolvedcritical38 min
2026-03-11 05:19 UTCAvailability issues in cluster fi-fredrikssonresolvedmajor1 h 32 min
2026-03-05 15:08 UTCThird party API failures causing site issuesresolvedminor3 h 50 min
2026-02-25 21:14 UTCAvailability issues with sites using external DNSresolvedminor4 min
2026-02-25 21:00 UTCNetworking issue in multiple clustersresolvednone0 min
2026-02-17 14:06 UTCAvailability issues in us-davis clusterresolvedmajor4 min
2026-02-06 13:18 UTCNetworking issues in cluster fi-coltraneresolvedminor3 h 04 min
2026-02-06 06:23 UTCActive DDoS campaignresolvedminor9 h 23 min
2026-02-03 13:13 UTCNetworking issues in cluster us-davisresolvedmajor47 min
2026-01-30 10:18 UTCNetworking issue in cluster fi-perkoresolvedmajor29 min
2026-01-30 06:59 UTCNetworking issue in cluster fi-perkoresolvedminor2 h 31 min
2026-01-29 20:01 UTCDatabase issue in fi-ellingtonresolvedminor19 min
2026-01-29 07:43 UTCAvailability issues in cluster fi-ellingtonresolvedminor45 min
2026-01-28 05:28 UTCAvailability issues in multiple clusterspostmortemmajor4 h 38 min
2026-01-23 03:46 UTCAvailability issues in cluster fi-perkoresolvedmajor19 min
2026-01-19 05:36 UTCNetworking issue in cluster fi-fredrikssonresolvedmajor34 min
2026-01-16 20:30 UTCAvailability issues in cluster fi-ellingtonresolvedmajor13 h 56 min
2025-12-19 05:14 UTCAvailability issues in cluster fi-fredrikssonresolvedminor56 min
2025-12-15 07:28 UTCAvailability issues in cluster se-brooresolvedmajor1 h 09 min
2025-12-09 01:14 UTCNetworking issue in cluster fi-fredrikssonresolvedmajor38 min
2025-12-07 09:41 UTCAvailability issues in cluster us-davisresolvednone49 min
2025-12-05 08:58 UTCClouldflare related availability issuesresolvedminor57 min
2025-12-03 16:49 UTCNetworking issue in cluster fi-ellingtonresolvednone13 min
2025-12-02 19:18 UTCDatabase issue in cluster fi-lahtiresolvedminor16 min
2025-11-30 14:19 UTCNetworking issue in cluster de-daunerresolvedminor3 h 01 min
2025-11-28 12:28 UTCNetwork issue in cluster fi-perkoresolvedminor48 min
2025-11-18 11:45 UTCClouldflare related availability issuesresolvedminor6 h 48 min
2025-11-06 12:00 UTCNetworking issue in cluster fi-haarlaresolvedmajor25 min
2025-11-04 19:11 UTCNetworking issue in cluster fi-coltraneresolvedmajor18 min
2025-11-04 12:29 UTCNetworking issue in cluster fi-fredrikssonresolvedminor59 min
2025-10-19 00:17 UTCNetworking issue in cluster fi-fredrikssonresolvedmajor16 min
2025-10-13 13:15 UTCNetworking issue in cluster fi-sestakresolvedmajor59 min
2025-10-06 12:02 UTCDatabase issue in cluster fi-tolonenresolvedmajor13 min
2025-09-29 10:34 UTCDatabase issue in cluster fi-ellingtonresolvedminor55 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
}