Vendor Status Watch

← all vendors

Lumaserv status history

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

0incidents, last 30 days
4incidents, last 90 days
14incidents on record
Incidents per week, last 12 weeks:

How long do Lumaserv incidents last?

60 minmedian incident duration13 measured
7.9 h90th percentile1 in 10 ran longer
2.0 hmedian, major/critical only3 incidents

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)

StartedIncidentStatusImpactDuration
2026-08-11 17:30 UTCZurich: Network Connectivity Issuesresolvedminor2 h 31 min
2026-07-22 09:20 UTCPacket Loss on certain hypervisorsresolvedminor7 h 54 min
2026-06-23 16:40 UTCBrief network disturbance in Frankfurt (FRA) during scheduled maintenanceresolvedmajor0 min
2026-06-19 09:46 UTCUpstream packet lossresolvednone2 h 49 min
2026-05-05 21:41 UTCInfo: DENIC Outageresolvedcritical9 h 54 min
2026-03-12 17:21 UTCService degration at ZRH1 (Zurich datacenter)resolvedminor3 min
2026-03-10 10:13 UTCMySQL database outageresolvedcritical2 h 01 min
2026-03-07 22:00 UTCPacket-loss during SDN configuration changesresolvednone16 min
2026-02-16 18:15 UTCNetwork outagepostmortemcritical1 h 15 min
2026-02-11 12:30 UTCDegraded connectivity between our locations at FRA and ZURresolvedminor0 min
2026-01-23 08:00 UTCPacket-loss on carrier-levelresolvedminor0 min
2025-11-26 09:50 UTCUpstream BGP Session Restart (No Impact)resolvednone1 h 00 min
2025-11-11 11:34 UTCHardware network link failure in FRA-2resolvednone1 h 00 min
2025-10-04 11:51 UTCPacket loss via routes of AS48314resolvednone28 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
}