We’ve heard from many of you about call logging failures, errors, and timeouts—especially our Bullhorn users. We sincerely apologize for these disruptions. Resolving these issues is our top priority, and we want to share what’s been happening behind the scenes.
What Happened?
- Traffic Throttling Issue – A recent system change meant to protect RingCentral from DDoS attacks was unintentionally too aggressive, blocking legitimate traffic.
- Server-Side Call Logging Load – Our beta feature requires more frequent syncing, which was overloading our servers—even for users who weren’t actively using it.
- Bullhorn Authentication Challenges – Bullhorn’s strict session timeouts make staying connected tricky. When authentication tokens refresh, they can create bottlenecks, leading to timeouts.
What We’ve Done to Fix It
✅ Tuned our load balancers to allow legitimate traffic through.
✅ Reduced unnecessary synchronization operations.
✅ Optimized our sync procedures to be more efficient.
✅ Working on improving Bullhorn authentication reliability.
✅ Exploring server upgrades to boost capacity.
The Results So Far
The good news: We’ve eliminated a major category of server errors (yellow line in the chart above) since Feb 17.
Yesterday’s spike in auth errors? We responded quickly with version 1.3.8, which is already reducing these issues. While you may need to re-login to Bullhorn more frequently, a simple browser refresh and reconnecting via Settings > Connect should resolve it.
We’re not done yet, but we believe in transparency. Please know we’re actively working to ensure a smoother experience. Thank you for your patience and trust.
Experiencing issues? Let us know in the comments or reach out to support.
