HackerOne status history
Current state: operational — “All Systems Operational” per https://www.hackeronestatus.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do HackerOne incidents last?
From 22 incidents with a vendor-posted start and resolve time. Longest on record: Analytics data freshness delay — 7.4 days (2025-09-19 03:00 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 (22)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-15 19:54 UTC | HackerOne Platform degradation: asset updates not propagating | resolved | major | 2 h 59 min |
| 2026-08-14 05:48 UTC | Degraded H1 performance | resolved | major | 1 h 11 min |
| 2026-08-07 14:51 UTC | Degraded H1 platform performance | resolved | none | 2 h 13 min |
| 2026-07-24 10:56 UTC | HackerOne platform down | resolved | major | 0 min |
| 2026-07-21 14:55 UTC | Degraded H1 platform performance | resolved | minor | 16 h 25 min |
| 2026-07-13 19:04 UTC | H1 Platform degraded performance | resolved | minor | 9 h 02 min |
| 2026-06-30 16:36 UTC | Degraded H1 platform performance | resolved | minor | 8 h 43 min |
| 2026-06-05 20:21 UTC | Data in dashboards and graphs not being updated | resolved | minor | 4 d 17 h |
| 2026-06-03 15:35 UTC | Errors when escalating reports through Integrations | resolved | major | 3 h 43 min |
| 2026-05-22 01:41 UTC | Degraded performance of H1 platform | resolved | minor | 3 h 10 min |
| 2026-04-22 12:30 UTC | Platform experiencing slowness | resolved | minor | 2 h 29 min |
| 2026-03-25 13:08 UTC | Degraded search functionality | resolved | major | 1 h 13 min |
| 2026-01-02 09:37 UTC | Users are unable to perform platform login | resolved | minor | 52 min |
| 2025-12-05 08:00 UTC | Cloudflare outage causing errors on www.hackerone.com | resolved | none | 0 min |
| 2025-11-18 14:20 UTC | Users are unable to perform platform login | resolved | major | 7 h 37 min |
| 2025-10-09 14:00 UTC | Hai tool use disruption | resolved | minor | 0 min |
| 2025-09-19 03:00 UTC | Analytics data freshness delay | resolved | minor | 7 d 9 h |
| 2025-09-18 12:28 UTC | Degraded Platform | resolved | critical | 4 d 2 h |
| 2025-09-17 10:05 UTC | API Down | resolved | critical | 1 h 20 min |
| 2025-09-08 11:11 UTC | HackerOne experiencing a service downtime | resolved | critical | 0 min |
| 2025-09-05 17:06 UTC | Increased error rate on HackerOne application | resolved | critical | 25 min |
| 2025-08-28 16:47 UTC | Impaired functionality in background job processing | resolved | major | 34 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 HackerOne with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"hackerone"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}