We have received reports of some users being unable to connect to Conquer Voice and experiencing failed or dropped calls. Affected users may see an "Invalid Request" message ("We're setting up your connection to Conquer Voice or you're already connected. Please refresh your page and wait 30 seconds to try again."), calls that disconnect immediately after clicking to dial, or calls that do not ring. Our teams are looking into these reports. We will update as more information becomes available.
UPDATE 9:15 AM PT: Our engineering team has identified the impacted systems and is working toward a solution.
UPDATE 9:20 AM PT: Our engineering team has patched the impacted systems and we are seeing operations return to normal. All users impacted should now be able to reconnect to Conquer Voice. Any users that still cannot connect, please submit a support ticket and we will assist you in reconnecting your dialer.
UPDATE 9:39 AM PT: Our team has been monitoring and has seen stable performance since the patch was put in place. An RCA will be posted when it becomes available.
RCA: On the morning of Monday, June 22, 2026, some Conquer Voice users experienced difficulty connecting to the dialer, along with a number of failed or dropped calls, over a period of approximately 80 minutes. Our team identified the cause and fully restored normal service the same morning.
We understand how important uninterrupted calling is to your teams, and we sincerely apologize for the disruption and any impact it caused. This document explains what happened, how we responded, and the steps we are taking to prevent it from happening again.
Impact
● Who was affected: A subset of users across multiple clients had trouble connecting to Conquer Voice during the window; some calls failed to connect or dropped.
● Duration: Approximately 80 minutes (10:33–11:51 AM ET), with the all-clear confirmed at 12:26 PM ET.
● Not affected: No customer data was lost, exposed, or compromised. The issue was limited to voice connectivity during the window; stored data and call records were not impacted.
Timeline of Our Response
All times Eastern Time (ET).
10:33 AM Conquer Support detected an increase in connection reports and began investigating.
10:54 AM Conquer Engineering was engaged.
11:14 AM A status notice was posted to the Conquer Support Portal.
11:32 AM Engineering identified the root cause.
11:33 AM A corrective change was applied to restore capacity.
11:51 AM Connections were flowing normally again; service confirmed stable.
12:26 PM Incident formally closed (all-clear).
What Happened
A portion of the infrastructure that handles voice connections reached a configured
capacity threshold during a period of heavy concurrent usage. Once that threshold
was reached, additional connection attempts routed to the affected components
were unable to complete, which produced the connection failures and dropped calls
that customers experienced.
How We Resolved It
Our Engineering team increased the available capacity on the affected components
and rebalanced call traffic across the environment to relieve the condition. Service
returned to normal within minutes of the change, and we verified stable operation
before closing the incident.
What We Are Doing to Prevent Recurrence
● Earlier detection: Adding proactive capacity monitoring and early-warning
alerts so our team is notified and can act before customers are affected.
● More headroom: Re-baselining capacity limits against real peak-usage levels
and increasing available headroom.
● Better load distribution: Improving how call traffic is balanced across the
environment so no single component becomes a bottleneck during peak
demand.
Our Commitment
The reliability of Conquer Voice is our highest priority, and this disruption fell short of
the standard we hold ourselves to. The preventative measures above are already
underway. If you have any questions or would like to discuss the impact to your
team, please reach out to your Customer Success Manager or Conquer Support, and
we will be glad to help
Comments
0 comments
Please sign in to leave a comment.