Vendor Status Watch

← all vendors

HackerOne status history

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

1incidents, last 30 days
7incidents, last 90 days
22incidents on record
Incidents per week, last 12 weeks:

How long do HackerOne incidents last?

2.4 hmedian incident duration22 measured
4.1 days90th percentile1 in 10 ran longer
73 minmedian, major/critical only11 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-15 19:54 UTCHackerOne Platform degradation: asset updates not propagatingresolvedmajor2 h 59 min
2026-08-14 05:48 UTCDegraded H1 performanceresolvedmajor1 h 11 min
2026-08-07 14:51 UTCDegraded H1 platform performanceresolvednone2 h 13 min
2026-07-24 10:56 UTCHackerOne platform downresolvedmajor0 min
2026-07-21 14:55 UTCDegraded H1 platform performanceresolvedminor16 h 25 min
2026-07-13 19:04 UTCH1 Platform degraded performanceresolvedminor9 h 02 min
2026-06-30 16:36 UTCDegraded H1 platform performanceresolvedminor8 h 43 min
2026-06-05 20:21 UTCData in dashboards and graphs not being updatedresolvedminor4 d 17 h
2026-06-03 15:35 UTCErrors when escalating reports through Integrationsresolvedmajor3 h 43 min
2026-05-22 01:41 UTCDegraded performance of H1 platformresolvedminor3 h 10 min
2026-04-22 12:30 UTCPlatform experiencing slownessresolvedminor2 h 29 min
2026-03-25 13:08 UTCDegraded search functionalityresolvedmajor1 h 13 min
2026-01-02 09:37 UTCUsers are unable to perform platform loginresolvedminor52 min
2025-12-05 08:00 UTCCloudflare outage causing errors on www.hackerone.comresolvednone0 min
2025-11-18 14:20 UTCUsers are unable to perform platform loginresolvedmajor7 h 37 min
2025-10-09 14:00 UTCHai tool use disruptionresolvedminor0 min
2025-09-19 03:00 UTCAnalytics data freshness delayresolvedminor7 d 9 h
2025-09-18 12:28 UTCDegraded Platformresolvedcritical4 d 2 h
2025-09-17 10:05 UTCAPI Downresolvedcritical1 h 20 min
2025-09-08 11:11 UTCHackerOne experiencing a service downtimeresolvedcritical0 min
2025-09-05 17:06 UTCIncreased error rate on HackerOne applicationresolvedcritical25 min
2025-08-28 16:47 UTCImpaired functionality in background job processingresolvedmajor34 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
}