Hive status history
Current state: operational — “All Systems Operational” per https://status.hive.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Hive incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-26 14:56 UTC | Home Page widget loading issues | resolved | major | 20 min |
| 2026-08-26 14:39 UTC | Home page and action loading issues | resolved | minor | 15 min |
| 2026-08-04 14:58 UTC | Degraded Performance across Hive Services | resolved | minor | 1 h 03 min |
| 2026-06-02 09:00 UTC | Delayed transactional emails due to third-party provider issue | resolved | major | 0 min |
| 2026-02-04 16:04 UTC | Infrastructure issues | resolved | major | 26 min |
| 2025-12-08 10:06 UTC | DNS issues for UK region | resolved | major | 6 h 23 min |
| 2025-09-30 14:17 UTC | Inability to access subset of services | resolved | major | 1 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
}