Huntress status history
Current state: degraded — “Partially Degraded Service” per https://huntressstatus.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Huntress incidents last?
From 45 incidents with a vendor-posted start and resolve time. Longest on record: ITDR Ingestion Delay — 24.2 h (2026-08-10 15:41 UTC). Excluded, never estimated: 1 still open / no resolve time. 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 (46)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-31 16:53 UTC | ITDR Ingestion Delay | monitoring | minor | open |
| 2026-08-19 19:02 UTC | ITDR Ingestion Delay | resolved | minor | 17 h 27 min |
| 2026-08-10 15:41 UTC | ITDR Ingestion Delay | resolved | minor | 24 h 10 min |
| 2026-08-05 14:17 UTC | ITDR Ingestion Delay | resolved | minor | 8 h 00 min |
| 2026-07-23 18:58 UTC | Elevated ITDR Signal Latency | resolved | minor | 1 h 04 min |
| 2026-07-02 00:57 UTC | Page Load Failures in Australia, New Zealand | resolved | major | 1 h 30 min |
| 2026-06-04 01:38 UTC | Signal processing delays | resolved | minor | 1 h 12 min |
| 2026-05-08 00:49 UTC | Portal Web Errors and Agent Communication Delays | resolved | major | 1 h 37 min |
| 2026-05-02 21:22 UTC | Automated Phone Notification Outage | resolved | minor | 4 h 15 min |
| 2026-04-25 02:03 UTC | Portal Degradation | resolved | minor | 9 h 57 min |
| 2026-04-21 16:43 UTC | Event processing delay | resolved | minor | 3 h 08 min |
| 2026-04-16 17:28 UTC | Services degraded | resolved | minor | 3 h 47 min |
| 2026-04-10 20:06 UTC | Web Portal Not Loading | resolved | critical | 40 min |
| 2026-04-01 17:14 UTC | Delay in Notification including Emails / PSA | resolved | critical | 19 min |
| 2026-03-19 16:24 UTC | Portal Web Errors | resolved | major | 33 min |
| 2026-03-19 02:08 UTC | Rio Processing Delay | resolved | minor | 1 h 28 min |
| 2026-03-18 19:32 UTC | ITDR Detections Are Catching Up | resolved | none | 5 h 13 min |
| 2026-03-17 13:17 UTC | Partial Service Outage | resolved | major | 1 h 08 min |
| 2026-03-16 22:13 UTC | Delays in SIEM Processing | resolved | minor | 3 h 00 min |
| 2026-03-16 16:38 UTC | Signal processing delays for SIEM data | resolved | minor | 1 h 42 min |
| 2026-03-13 16:30 UTC | Portal outage | resolved | none | 0 min |
| 2026-03-11 13:48 UTC | Customer Messaging Delay | resolved | minor | 23 min |
| 2026-03-02 23:39 UTC | Degraded ITDR Assisted Remediations | resolved | major | 22 h 15 min |
| 2026-02-05 16:04 UTC | Portal outage | resolved | major | 12 min |
| 2026-02-04 01:12 UTC | Portal & agent communication issues | resolved | major | 15 h 34 min |
| 2026-02-02 13:14 UTC | Delayed data processing | resolved | minor | 12 h 25 min |
| 2026-01-31 10:01 UTC | SIEM Database Outage | resolved | major | 1 h 32 min |
| 2026-01-29 14:44 UTC | Live support chat is degraded | resolved | minor | 2 h 28 min |
| 2026-01-28 22:13 UTC | Portal outage | resolved | major | 2 h 05 min |
| 2026-01-22 21:34 UTC | ITDR Onboarding Degradation | resolved | major | 6 h 57 min |
| 2026-01-21 19:06 UTC | Portal Degradation | resolved | major | 24 min |
| 2025-12-05 23:00 UTC | ITDR ingest delays | resolved | minor | 3 h 14 min |
| 2025-12-03 21:07 UTC | ITDR ingest delays | resolved | minor | 21 h 24 min |
| 2025-11-18 13:28 UTC | Operational issues reported by Cloudflare | resolved | major | 2 h 36 min |
| 2025-10-29 16:36 UTC | Upstream ITDR Outage | resolved | major | 13 h 21 min |
| 2025-10-28 17:32 UTC | Partial ITDR Detection Outage | resolved | major | 4 h 40 min |
| 2025-10-20 20:02 UTC | Learners not receiving credit for completing assignments | resolved | minor | 2 h 41 min |
| 2025-10-20 17:06 UTC | Increased signal processing latency | resolved | minor | 19 h 56 min |
| 2025-10-20 11:55 UTC | Process Insights Processing Delay | resolved | minor | 4 h 16 min |
| 2025-10-16 17:26 UTC | Signal processing delays for persistent footholds processing | resolved | minor | 5 h 35 min |
| 2025-10-15 16:12 UTC | Signal processing delays for persistent footholds processing | resolved | minor | 15 h 01 min |
| 2025-09-30 20:18 UTC | Signal processing delays for process insights data | resolved | major | 5 h 41 min |
| 2025-09-08 14:01 UTC | Intermittent Portal 502s | resolved | minor | 8 h 36 min |
| 2025-09-05 19:21 UTC | Intermittent Portal 502s | resolved | minor | 4 h 24 min |
| 2025-09-03 23:38 UTC | Portal users unable to chat with support | resolved | minor | 15 h 54 min |
| 2025-09-02 16:05 UTC | SAT Outage | resolved | critical | 2 h 02 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 Huntress with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"huntress"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}