Huntress logo

Is Huntress Down?

SecurityLive status, outages, and incident history

No. Huntress is up right now.

Every monitored Huntress system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Huntress breaks

Huntress is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

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

Official Huntress status page
How we know: the official Huntress status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Huntress Component Status

The main Huntress systems on this page. All 7 are operational right now.

7operational
Agent Deployment and Communication
Operational
Huntress Web
Operational
Incident Reports
Operational

4 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking ITDR, Management Portal, Security Awareness Training, SIEM.

See all of them free

Component statuses may change independently during partial outages.

Recent Huntress Outages & Incidents

Incident history from the official Huntress status page, including resolution updates.

ITDR Ingestion DelayResolved Aug 31, 2026 · 484h 25mResolved

Microsoft 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. --- [2026-09-17T15:18:50.916Z] (monitoring) Our partners at Microsoft have deployed a fix for the affected customers which will roll out over the remainder of this week and into the weekend. We will continue working with them to verify the fix is working as intended. --- [2026-09-16T14:53:21.537Z] (monitoring) Our partners at Microsoft are in the process of rolling out a fix across the affected tenants. We are monitoring the effect and providing information to them on the effectiveness of this solution. --- [2026-09-14T18:49:55.372Z] (monitoring) We are continuing to work with Microsoft to resolve the intermittent delays for a small set of affected customers. --- [2026-09-11T15:55:10.993Z] (monitoring) We are continuing to provide information about any affected customers to our partners at Microsoft. Intermittent delays continue to show up for a small set of affected customers. --- [2026-09-01T22:09:11.354Z] (monitoring) We're continuing to work with our partners at Microsoft, who have identified the cause of the delay and are in the process of implementing a fix. We are still seeing intermittent delays of up to 4 hours for some customers. We will continue to provide updates as soon as more information becomes available. --- [2026-08-31T17:37:39.798Z] (identified) We've identified that the cause of our ingestion delay is from a degradation in Microsoft's M365 APIs. No GWS customer are affected. We're working through our partner channels to get this resolved, and will update this page as soon as we know more information. --- [2026-08-31T16:53:14.221Z] (investigating) We have noticed a slight delay in our ITDR ingestion pipeline, and are investigating the cause.

ITDR Ingestion DelayResolved Aug 19, 2026 · 17h 27mResolved

We're no longer experiencing delays from our upstream provider. This incident has been resolved. --- [2026-08-20T01:24:21.032Z] (monitoring) While we have seen an improvement in overall ingestion timing, we are still seeing delayed events from our upstream provider. We're currently working with them to resolve the issue. We will continue monitoring, and posting updates as we have them. --- [2026-08-19T21:14:32.509Z] (monitoring) We are seeing improvements in our ingestion timing and continuing to monitor for a resolution from our upstream provider. We will continue to publish updates as we have them. --- [2026-08-19T20:10:15.454Z] (monitoring) We are still seeing delays from our upstream provider leading to ITDR ingestion delay and are continuing to monitor the situation. --- [2026-08-19T19:02:30.014Z] (monitoring) We've identified an issue with an upstream provider that is resulting in ITDR ingestion latency and are actively monitoring the situation.

ITDR Ingestion DelayResolved Aug 10, 2026 · 24h 10mResolved

This incident has been resolved. --- [2026-08-10T20:28:46.156Z] (identified) We've identified an issue with an upstream provider that is resulting in ITDR ingestion latency and errors in the Huntress portal and are working on mitigations. --- [2026-08-10T20:21:29.344Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-08-10T15:41:55.856Z] (investigating) We are currently investigating this issue.

Huntress Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Huntress incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 25 days with incidentsSep 25

Live Huntress Outage Reports

Problems reported by engineers using Huntress. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Huntress problems reported yet.

Something wrong with Huntress on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Huntress

Is Huntress down? Huntress reports live availability for 7 components at status.huntress.com, among them Management Portal (huntress.io), Huntress Web (huntress.com) and Agent Deployment and Communication. Track Huntress outages, degradations and past incidents here, with uptime history and alerts across your security stack.

Over the past 30 days, PulsAPI has measured Huntress uptime at 100.00%. Response times, incident history, and SLA tracking for Huntress are available on the PulsAPI dashboard.

Huntress Status FAQ

Is Huntress down right now?

The verdict at the top of this page comes from the latest poll of the official Huntress status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Huntress is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Huntress recovers.

How do I check Huntress uptime history?

PulsAPI tracks Huntress uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Huntress changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Huntress outages?

PulsAPI reads the official Huntress status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Huntress components?

Yes. PulsAPI monitors 7 individual Huntress components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Huntress goes down?

Yes. Create a free account and subscribe to Huntress: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Huntress to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Huntress problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Huntress?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Huntress plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Huntress with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services