Hoxhunt Outage History

Hoxhunt experienced a major incident where all link-based training packages (XSAT) became inaccessible, displaying "Training not available!" error messages even for correctly published packages. The issue affected the core Hoxhunt service and prevented users from accessing any link-based training content. The incident was resolved after 1.5 hours with developers implementing an immediate fix.

Hoxhunt experienced an 11-minute service incident where individual user pages in User Management and the Agents page under Automations were inaccessible, displaying "Response not successful: Received status code 400" errors. While user lists remained viewable, users could not access detailed individual user pages during the outage. The issue was investigated and resolved, with all affected pages now loading normally.

Some Hoxhunt users experienced "Something went wrong" or "servers busy" error messages when attempting to report emails and view Instant Feedback. The incident affected the email reporting and feedback functionality for a subset of users over a 23.2-hour period. The root cause was identified and a fix was deployed, restoring normal operation to all affected components.

The Hoxhunt External GraphQL API documentation became inaccessible through the direct web URL (https://app.hoxhunt.com/docs/graphql-external/), affecting developers trying to access API documentation. Users could still access the API docs through GraphQL clients like Altair, Insomnia, and Postman as a workaround. The issue was resolved within 12 minutes.

A code change caused the Benchmarks page in Hoxhunt's Admin portal to fail loading for some organizations, initially affecting the Inactive tab and later expanding to the Active tab for a smaller subset of customers. Users encountered "Could not fetch benchmarks" errors when trying to access benchmark data through the admin interface. The issue was resolved after 20.3 hours with a follow-up code release, while benchmark email deliveries and the alternative Insights portal remained unaffected throughout the incident.

Hoxhunt experienced a 20.7-hour data processing delay that affected CxO Reports in Insights, Cloud Export datasets, and Hoxhunt Reports, with users encountering errors when trying to filter reports by previous day data. The Data Engineering team re-processed the affected data to restore up-to-date information across all reporting systems. All reports and datasets were fully updated and the incident was resolved.

Hoxhunt's Response portal experienced a complete outage for 18 minutes due to an infrastructure configuration change that failed to apply correctly. The incident affected all Response portal components including Threat Feed, Incident Orchestration, and Feedback Rules, preventing users from accessing response.hoxhunt.com and its subpages. The issue was resolved by fixing the failed configuration change, restoring full functionality to the portal.

Hoxhunt's Instant Feedback feature experienced a visual display issue where users encountered "Page Not Found" errors when trying to view feedback after reporting suspicious emails, though the underlying data processing continued to work correctly. The incident lasted 1.9 hours and was resolved with a fix that restored normal Instant Feedback functionality. Users were advised they could review any missed feedback information through the Hoxhunt Dashboard under Reported Threats.

Hoxhunt experienced a 4.5-hour issue where quiz modules owned by Hoxhunt were not visible to administrators and could not be assigned to new training packages, also impacting quiz completions within simulation micro-trainings. The problem affected the availability of standard security awareness training content and modules within training libraries for organizations. The issue was identified and resolved with a fix, while custom training content created by organizations remained unaffected throughout the incident.

Users experienced an issue accessing XSAT training packages that contained custom training content on the Hoxhunt platform. The incident lasted 54 minutes while developers identified the root cause and implemented a fix. The issue was resolved and XSAT training access returned to normal functionality.