Live / Bullhorn / Incident
Bullhorn: Bullhorn ATS/CRM – Service Notice: REST API Connectivity
Bullhorn · bullhorn.comResolved2026-11-11 12:57 UTC
Public — what happened
Summary
Bullhorn said some users of its ATS/CRM product might have trouble with REST API authentication, with all clusters and services listed as affected. The notice began at 04:37 UTC on 2026-11-11, and the company's technical operations team said it was investigating. At 06:01 UTC Bullhorn said a fix was in place and it was monitoring, and it repeated that it was watching for further problems at 06:30 UTC. At 12:57 UTC it said it was investigating the issue again, and the incident is not marked resolved; no cause was given.
Affected
CLS20, CLS21, CLS22, CLS23, CLS30, CLS31, CLS32, CLS33, CLS34, CLS35, CLS40, CLS41, CLS42, CLS43, CLS44, CLS45, CLS61, CLS62, CLS71, CLS72
Timeline
- Started — 2026-11-11 04:37 UTC
- Investigating — 2026-11-11 04:37 UTC
- Monitoring — 2026-11-11 06:01 UTC (2 updates)
- Investigating — 2026-11-11 12:57 UTC
- Resolved — 2026-11-11 12:57 UTC · 8h 20m 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 47, 2026, our weekly internet health report.