Live / Bullhorn / Incident
Bullhorn: Bullhorn ATS/CRM - Performance Issues
Bullhorn · bullhorn.comMajor incidentResolved2026-10-21 23:37 UTC
Public — what happened
Summary
Bullhorn said some users of its ATS/CRM product could see slowness or errors when signing in or using the application, and it listed all clusters as affected. The company reported the problem starting at 18:45 UTC on 2026-10-21 and said its technical operations team was investigating, still doing so at 20:54 UTC. At 22:30 UTC Bullhorn said a fix had been put in place and it was watching the results, and the incident was marked resolved at 23:37. No cause was given in the text provided.
Affected
CLS20, CLS21, CLS22, CLS23, CLS30, CLS31, CLS32, CLS33, CLS34, CLS35, CLS40, CLS41, CLS42, CLS43, CLS44, CLS45, CLS50, CLS61, CLS62, CLS71, CLS72
Timeline
- Started — 2026-10-21 18:45 UTC
- Investigating — 2026-10-21 18:45 UTC (2 updates)
- Monitoring — 2026-10-21 22:30 UTC
- Resolved — 2026-10-21 23:37 UTC · 4h 51m after it started
With SquidGrid — where it starts on the route
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 seeCustomers 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.