It looks like we have recieved no inbound calls since Oct 6. When you dail in, it says "Concurrency Limit Reached" and hangs up. We're hard down due to this issue. Our Org ID is fa3549c9-cea8-439c-9cf1-4643c64857c0

Thank you for sharing the details. To help diagnose the "Concurrency Limit Reached" issue, could you please confirm if you have checked your server's

/health

endpoint to see the current values for

activeCalls

,

callsInQueue

, and

maxConcurrency

? This will help determine if the concurrency counter is stuck or if there is another underlying issue. If you haven't checked yet, you can do so by running:

curl https://your-server.com/health

Let me know what values you see, or if you need help with this step. Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)

@Vapi Support Bot we are not running a standalone server for VAPI yet

Since you're not running a standalone server, please log in to the [Vapi Dashboard](https://dashboard.vapi.ai/calls) and check your call logs and concurrency status. Look for any stuck active calls or errors in the logs. If the dashboard shows no active calls but you still receive "Concurrency Limit Reached," contact Vapi support with your Org ID and a brief description—they can help reset your concurrency counter if needed. Sources: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management) - [Debugging voice agents](https://docs.vapi.ai/debugging)

@Vapi ^^

We have reset your concurrency counter. Please consider using the phone numbers page for performing outbound calls to prevent the limit from being hit