Vendor Status Watch

← all vendors

Hornetsecurity status history

Current state: operational — “Operational” per https://status.hornetsecurity.com (Status.io), checked 2026-09-24 12:28 UTC.

5incidents, last 30 days
5incidents, last 90 days
5incidents on record
Incidents per week, last 12 weeks:

Status.io only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Hornetsecurity. It fills in from here.

Get Hornetsecurity alerts in your Slack — free templateRSS for Hornetsecurity

Incidents on record (5)

StartedIncidentStatusImpactDuration
2026-09-17 08:31 UTC[HSE20260917-01-I] Incident: Service Disruption: Hornetsecurity Websiteinvestigating—27 h 56 min (approx.)
2026-09-16 13:16 UTCHornet.email Security Maintanancemaintenancemaintenance6 d 18 h (approx.)
2026-09-13 10:48 UTC[HSE20260913-01-I] Incident: Partial Service Disruption: 365 Total Backup Service (DE Region) investigating—25 h 40 min (approx.)
2026-09-09 06:52 UTC[HSE20260923-01-M] Maintenance: Control Panel 6.63.0.0maintenancemaintenance14 d 5 h (approx.)
2026-09-08 12:41 UTC[HSE20260916-01-M] Scheduled Maintenance: 365 Total Backup Service (DE & UK Regions)maintenancemaintenance12 d 23 h (approx.)

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 Hornetsecurity with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "hornetsecurity"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}