Live  /  Bullhorn  /  Incident

Bullhorn: Bullhorn Incident Updates - BBO

Bullhorn · bullhorn.comMajor incidentResolved2026-10-23 14:58 UTC
Public — what happened

Summary

Bullhorn reported a major incident affecting access to BBO, beginning at 14:56 UTC on 2026-10-22. The company said it identified the problem and was working on a fix, and by 14:58 UTC on 2026-10-23 it stated that access had been restored. Bullhorn said it found the root cause of a single sign-on problem for people reaching BBO through its ATS, and asked anyone still unable to sign in to open a support case. It also said some users coming in through ATS/CRM might see CAPTCHA prompts, and the incident was still listed as not resolved.

Affected

BBO GRR, BBO SYD, BBO UK

As listed on Bullhorn’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Bullhorn against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Bullhorn: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Bullhorn report →

More from Bullhorn

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Bullhorn status & history page.

Related: Bullhorn status & history. SquidGrid is not affiliated with Bullhorn.