Huntress Outage History

52 incidents recorded over the last 365 days, 42 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Huntress status100.00% uptime history

Every Recorded Huntress Incident

Huntress incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026Delay in sending some ITDR escalationsAffected ITDR escalations have been fixed and events are being processed normally.2h 48mResolved
Nov 2, 2026SAT Performance IssuesThis incident has been resolved.37 minResolved
Oct 30, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Oct 28, 2026Elevated Processing DelaysThis incident has been resolved.1h 9mResolved
Oct 22, 2026Processing delaysThis incident has been resolved.5h 8mResolved
Oct 21, 2026Curricula Simulated Phish Service is down.This incident has been resolved.3h 27mResolved
Oct 15, 2026Partial ITDR Ingestion Delay for M365 EventsMicrosoft 365 identity events are being received within normal ranges. Delayed events have been processed, and identity detections and incident reports are current. We are resolving this incident.20h 41mResolved
Oct 1, 2026Signal generation and SOC response delayThis incident has been resolved.4h 3mResolved
Sep 30, 2026ITDR Event Ingestion DelayData ingest lag from Microsoft has been resolved.53h 46mResolved
Aug 31, 2026ITDR Ingestion DelayMicrosoft has deployed additional fixes to their infrastructure, and our internal telemetry is back to showing normal ingest timing for events. This incident is now resolved.484h 25mResolved
Aug 19, 2026ITDR Ingestion DelayWe're no longer experiencing delays from our upstream provider. This incident has been resolved.17h 27mResolved
Aug 10, 2026ITDR Ingestion DelayThis incident has been resolved.24h 10mResolved
Aug 5, 2026ITDR Ingestion DelayThe upstream latency issues are resolving. Huntress ingestion is operating normally.8h 0mResolved
Jul 23, 2026Elevated ITDR Signal LatencyThis incident has been resolved.1h 4mResolved
Jul 2, 2026Page Load Failures in Australia, New ZealandThis incident has been resolved.1h 30mResolved
Jun 4, 2026Signal processing delaysThis incident has been resolved.1h 12mResolved
May 29, 2026Curricula Support Email MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
May 22, 2026Database MaintenanceThis maintenance window has been postponed to Wednesday next week.1h 0mScheduled
May 15, 2026Database MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
May 14, 2026Database MaintenanceThe scheduled maintenance has been completed.3h 0mScheduled
May 8, 2026Portal Web Errors and Agent Communication DelaysWe have shifted resources off of the affected AWS zone and are not seeing any further issues.1h 37mResolved
May 2, 2026Automated Phone Notification OutageThis incident has been resolved.4h 15mResolved
Apr 25, 2026Portal DegradationThis incident has been resolved.9h 57mResolved
Apr 21, 2026Event processing delayThis incident has been resolved.3h 8mResolved
Apr 16, 2026Services degradedThis incident has been resolved.3h 47mResolved
Apr 10, 2026Web Portal Not LoadingThis incident has been resolved.40 minResolved
Apr 1, 2026Delay in Notification including Emails / PSAThis incident has been resolved.19 minResolved
Mar 29, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 28, 2026Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 19, 2026Portal Web ErrorsThis incident has been resolved.33 minResolved
Mar 19, 2026Rio Processing DelayThis incident has been resolved.1h 28mResolved
Mar 18, 2026ITDR Detections Are Catching UpThis incident has been resolved.5h 13mResolved
Mar 17, 2026Partial Service OutageThis incident has been resolved.1h 8mResolved
Mar 16, 2026Delays in SIEM ProcessingAll components are operating normally.3h 0mResolved
Mar 16, 2026Signal processing delays for SIEM dataThis incident has been resolved.1h 42mResolved
Mar 13, 2026Portal outageWe have rolled out the fix to the Huntress portal and are seeing resolution across the board.-32 minResolved
Mar 11, 2026Customer Messaging DelayThis incident has been resolved.23 minResolved
Mar 5, 2026Database maintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 5, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Mar 2, 2026Degraded ITDR Assisted RemediationsThis incident has been resolved.22h 15mResolved
Feb 28, 2026Database MaintenanceThe scheduled maintenance has been completed.1h 0mScheduled
Feb 5, 2026Portal outageWe have rolled out the fix to the Huntress portal and are seeing resolution across the board.12 minResolved
Feb 4, 2026Portal & agent communication issuesThis incident has been resolved.15h 34mResolved
Feb 2, 2026Delayed data processingThis incident has been resolved.12h 25mResolved
Jan 31, 2026SIEM Database OutageThis incident has been resolved.1h 32mResolved
Jan 29, 2026Live support chat is degradedThis incident has been resolved.2h 28mResolved
Jan 28, 2026Portal outageThis incident has been resolved.2h 5mResolved
Jan 22, 2026ITDR Onboarding DegradationThis incident has been resolved.6h 57mResolved
Jan 21, 2026Portal DegradationThis incident has been resolved.24 minResolved
Dec 5, 2025ITDR ingest delaysThis incident has been resolved.3h 14mResolved
Dec 3, 2025ITDR ingest delaysThis incident has been resolved.21h 24mResolved
Nov 18, 2025Operational issues reported by CloudflareThis incident has been resolved.0 minResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Huntress incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Huntress Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Huntress acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Huntress outage in this window ran 20d 4h, against a mean recovery of 15h 5m. If you depend on Huntress in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.