Vendor Status Watch

← all vendors

Hive status history

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

2incidents, last 30 days
3incidents, last 90 days
7incidents on record
Incidents per week, last 12 weeks:

How long do Hive incidents last?

26 minmedian incident duration7 measured
87 min90th percentile1 in 10 ran longer
26 minmedian, major/critical only5 incidents

From 7 incidents with a vendor-posted start and resolve time. Longest on record: DNS issues for UK region — 6.4 h (2025-12-08 10:06 UTC). Excluded, never estimated: nothing. 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 (7)

StartedIncidentStatusImpactDuration
2026-08-26 14:56 UTCHome Page widget loading issuesresolvedmajor20 min
2026-08-26 14:39 UTCHome page and action loading issuesresolvedminor15 min
2026-08-04 14:58 UTCDegraded Performance across Hive Servicesresolvedminor1 h 03 min
2026-06-02 09:00 UTCDelayed transactional emails due to third-party provider issueresolvedmajor0 min
2026-02-04 16:04 UTCInfrastructure issuesresolvedmajor26 min
2025-12-08 10:06 UTCDNS issues for UK regionresolvedmajor6 h 23 min
2025-09-30 14:17 UTCInability to access subset of servicesresolvedmajor1 h 27 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 Hive with the template

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

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