Unrated
identified
since
Delay in sending some ITDR escalations
We are aware of a delay in sending some ITDR escalations. A fix is rolling out now, and we will post an update when escalations are back to normal.
Latest update 11 minutes ago
Is Huntress Down?
Partially — Huntress is degraded
- Huntress's status page
- Open incident · unrated incident (“Delay in sending some ITDR escalations”)
- FlareWarden checks
- Website reachable · 8 of 8 regions · 530 ms
Right now
The verdict is the worse of these two. How we decide
Huntress's status page
status.huntress.com · read · checked every 3 minutes
| Component | Status |
|---|---|
| Management Portal (huntress.io) | Operational |
| Huntress Web (huntress.com) | Operational |
| Agent Deployment and Communication | Operational |
| Security Awareness Training | Operational |
| Incident Reports | Operational |
| ITDR | Operational |
| SIEM | Operational |
| Curricula Simulated Phishing Server | Operational |
FlareWarden checks
huntress.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 530 ms
- Checked
By region
- Amsterdam reachable, 535 ms
- Dallas reachable, 383 ms
- Newark reachable, 149 ms
- Paris reachable, 716 ms
- San Jose reachable, 433 ms
- Stockholm reachable, 627 ms
- Sydney reachable, 1233 ms
- Toronto reachable, 167 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Amsterdam | 29 ms | 97 ms | 196 ms | 535 ms |
| Dallas | 179 ms | 37 ms | 76 ms | 346 ms |
| Newark | 97 ms | 7 ms | 16 ms | 149 ms |
| Paris | 17 ms | 120 ms | 268 ms | 716 ms |
| San Jose | 62 ms | 80 ms | 141 ms | 432 ms |
| Stockholm | 40 ms | 109 ms | 220 ms | 506 ms |
| Sydney | 223 ms | 199 ms | 402 ms | 1233 ms |
| Toronto | 66 ms | 17 ms | 36 ms | 166 ms |
We check that huntress.io loads, not every feature behind it.
Test it yourself
History
Incidents Huntress reported
Since Oct 27, 8 days · from status.huntress.com
- Incidents
- 3
- Major or critical
- 1
- Median to resolve
- 53m
- Ongoing
- lasted 37m
major ·
- lasted 1h 9m
Unrated ·
Huntress website availability
Measured by FlareWarden · huntress.io
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 622ms
Last 30 days
7-day clean streakOct 5
Today
No downtime
Partial
Downtime
Not measurable
No data
Measured by FlareWarden's own checks of huntress.io from multiple regions every 6 hours. Huntress's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 7 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Huntress does
Huntress is a managed security platform used by IT teams and managed service providers. The Huntress Agent on each endpoint feeds Managed EDR, while Managed ITDR watches Microsoft 365 and Google Workspace identities and a SIEM collects logs. A 24x7 Security Operations Center investigates what the platform finds and writes incident reports. Admins work in the Huntress Management Console at huntress.io, where agents also check in for tasks such as host isolation.
What an outage looks like
The Management Console at huntress.io shows web errors or will not load, agents stop checking in on time, and incident reports or ITDR signals arrive late. Huntress's status page tracks the portal, huntress.com, agent communication, incident reports, ITDR, SIEM and Security Awareness Training separately. On May 8, 2026 an AWS outage caused portal errors and agent communication delays across seven components; on October 1, 2026 delayed signal generation slowed SOC response for about four hours.
What to do about it
Check status.huntress.com and see which component is affected: an ITDR row with a Microsoft ingestion note means the delay is upstream. If the page is clear, Huntress asks you to open a support ticket so it can investigate and update the page. Product support takes email at support@huntress.com and chat from the Help button. For an incident report, email incidents@huntress.com; if you cannot reach the dashboard, start a live chat at support.huntress.io and pick SOC Support.
Is it down for everyone, or just you?
If this page says Huntress is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Huntress outage FAQ
Does a Huntress portal outage stop the agent from receiving tasks?
It can slow them. Huntress's docs say agents pick up tasks such as host isolation, Defender scans and file collection from eetee.huntress.io within seconds, and fall back to checking the portal at huntress.io every 15 minutes when that service is unreachable. On May 8, 2026 Huntress reported portal web errors and agent communication delays together, during an AWS outage that Huntress worked around by moving off the affected AWS zone.
Why are my Huntress ITDR alerts delayed when the status page shows Microsoft?
Because ITDR depends on events Microsoft sends to Huntress. From September 30 to October 3, 2026 Huntress reported an ITDR ingestion delay caused by lag in events from Microsoft, and said it was working with Microsoft until the latency dropped. ITDR has its own row on the status page, and Huntress posted further ITDR ingestion delays on August 5, August 19 and August 31, 2026.
How do I reach the Huntress SOC during an outage?
Email incidents@huntress.com or use chat. Huntress's docs say an Account Admin or Security Engineer can press Request SOC Support on a critical incident report for email, chat or a callback, and callbacks only ever come from 1-833-486-8669. If the dashboard will not load, open live chat at support.huntress.io, choose Get in Touch, then Live Chat, and select SOC Support.
How long do Huntress outages usually last?
The portal incidents on Huntress's status page this year lasted hours, not days. Page load failures for users in Australia and New Zealand on July 2, 2026 ran from 00:57 to 02:28 UTC, and the May 8, 2026 portal and agent incident about 1 hour 40 minutes. Ingestion delays that depend on Microsoft have run longer: the September 30 ITDR delay was resolved on October 3, 2026.
What does the check on this page measure?
It loads huntress.io, the sign-in page of the Huntress Management Console, which Huntress's status page tracks as Management Portal (huntress.io). It is not a redirect to huntress.com. It does not sign in, reach an agent, deliver a task, or test ITDR, SIEM or SOC response, so a green result means the console's front door answers, not that signals and incident reports are on time.
How we measure this
- We request Huntress's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Huntress publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Huntress itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Huntress goes down
We check Huntress every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free MonitoringFree plan available
No credit card required