Lumaserv status history
Current state: operational — “All Systems Operational” per https://status.lumaserv.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Lumaserv incidents last?
From 13 incidents with a vendor-posted start and resolve time. Longest on record: Info: DENIC Outage — 9.9 h (2026-05-05 21:41 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 (14)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-11 17:30 UTC | Zurich: Network Connectivity Issues | resolved | minor | 2 h 31 min |
| 2026-07-22 09:20 UTC | Packet Loss on certain hypervisors | resolved | minor | 7 h 54 min |
| 2026-06-23 16:40 UTC | Brief network disturbance in Frankfurt (FRA) during scheduled maintenance | resolved | major | 0 min |
| 2026-06-19 09:46 UTC | Upstream packet loss | resolved | none | 2 h 49 min |
| 2026-05-05 21:41 UTC | Info: DENIC Outage | resolved | critical | 9 h 54 min |
| 2026-03-12 17:21 UTC | Service degration at ZRH1 (Zurich datacenter) | resolved | minor | 3 min |
| 2026-03-10 10:13 UTC | MySQL database outage | resolved | critical | 2 h 01 min |
| 2026-03-07 22:00 UTC | Packet-loss during SDN configuration changes | resolved | none | 16 min |
| 2026-02-16 18:15 UTC | Network outage | postmortem | critical | 1 h 15 min |
| 2026-02-11 12:30 UTC | Degraded connectivity between our locations at FRA and ZUR | resolved | minor | 0 min |
| 2026-01-23 08:00 UTC | Packet-loss on carrier-level | resolved | minor | 0 min |
| 2025-11-26 09:50 UTC | Upstream BGP Session Restart (No Impact) | resolved | none | 1 h 00 min |
| 2025-11-11 11:34 UTC | Hardware network link failure in FRA-2 | resolved | none | 1 h 00 min |
| 2025-10-04 11:51 UTC | Packet loss via routes of AS48314 | resolved | none | 28 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 Lumaserv with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"lumaserv"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}