Status
Exploit Hound Service Status
Operational status for the services Exploit Hound operates. Every state below is measured when you load this page.
Onsite probes and OS clients run inside customer environments. Their health is reported per deployment inside the console, not here — a quiet collector is a question about one customer’s network rather than about this platform.
Hosted services
Loading current status… If this does not update, the status endpoint is unreachable from your browser — which is itself worth knowing, and is not the same as the platform being down.
Independent measurement
Loading…
Current incidents
Loading…
Planned maintenance
Loading…
Resolved incidents
Loading…
Reporting and questions
Something looks wrong
If you are seeing behaviour this page does not reflect, tell us rather than waiting for a component to change state. A report from someone using the platform is often earlier than a check.
Security review
Architecture, data flow, tenant isolation, credential handling, subprocessors and current dependency posture are answered as part of a security review, including standard vendor questionnaires.
What this page covers
Hosted platform — ours
Ingestion, correlation, attack-path analysis, Fix First, reporting and the MSP console. Exploit Hound operates these, so their state belongs on this page.
Onsite probe and OS clients — in the customer environment
These run where the assets are and report into the platform. A probe that goes quiet may be a firewall change, a rebooted host or an ISP; calling that an Exploit Hound incident would make the real ones less believable. Their status is per deployment, in the console.
Start with what's actually exposed.
Point Exploit Hound at the assets you are authorized to assess and see the connected picture, ranked by what removes the most exposure.