| ID | Start Time (UTC) | End Time (UTC) | |--------------------------------------|-------------------------------|-------------------------------| | 019af829-bdbb-744b-82de-b11e874a74a2 | 2025-12-07 09:34:36 GMT+0 | 2025-12-07 09:35:32 GMT+0 | | 019af82a-b35a-7113-b889-9e37c7913073 | 2025-12-07 09:35:39 GMT+0 | 2025-12-07 09:36:34 GMT+0 | | 019af82a-bdb0-7881-b722-6b280ded721c | 2025-12-07 09:35:42 GMT+0 | 2025-12-07 09:36:36 GMT+0 | | 019af82a-c7c7-7113-a045-1cab63f6edbb | 2025-12-07 09:35:44 GMT+0 | 2025-12-07 09:38:13 GMT+0 | | 019af82a-d270-7113-b889-a70d3b621196 | 2025-12-07 09:35:47 GMT+0 | 2025-12-07 09:36:15 GMT+0 | | 019af82a-e8bc-7881-b722-84eca0fdc8fd | 2025-12-07 09:35:53 GMT+0 | 2025-12-07 09:37:43 GMT+0 | | 019af82a-fbc3-7119-88e7-90516a16db77 | 2025-12-07 09:35:57 GMT+0 | 2025-12-07 09:36:59 GMT+0 | | 019af82b-168a-7003-8ead-b94d271eded6 | 2025-12-07 09:36:04 GMT+0 | 2025-12-07 09:36:56 GMT+0 | | 019af82b-aa98-7003-8ead-eee73349633a | 2025-12-07 09:36:42 GMT+0 | 2025-12-07 09:37:14 GMT+0 | | 019af82b-c452-7eef-956f-29a0c1dd22ae | 2025-12-07 09:36:49 GMT+0 | 2025-12-07 09:37:49 GMT+0 | at 2025-12-07 9:38 TIME STAMP I have trigger 4 calls and all of them failed with concurrecy issue, but at that time the available were 7. The yellow ones have been completed by the said timestamp, where the error has been thrown. Folks Please Help me understand If I missed something or fix this issue. Thank you much!! 👀 org ID : 3ba2859e-36e2-4306-be9a-bbfd42ed38a6 https://cdn.discordapp.com/attachments/1447670493963358208/1447670494437576725/Screenshot_2025-12-09_at_12.53.46_AM.png?ex=69410976&is=693fb7f6&hm=11e08963c00e5903794dbb8ee6d9d1ffc7f264390ac21710e4c6817e8660deb2&

Action Step: Check your current concurrency limits in the Vapi Dashboard under billing settings, as recent updates may have changed how limits are calculated and enforced. - Go to: Settings → Billing in your [Vapi Dashboard](https://dashboard.vapi.ai/settings/billing) - Compare the values for

concurrencyLimitIncluded

and

concurrencyLimitPurchased

to ensure your available capacity matches your expectations. If you find a mismatch, document the values and share them with support for further investigation. This step addresses recent changes that could cause concurrency tracking discrepancies ([see changelog](https://docs.vapi.ai/changelog/2024/11/11)). Source: - [Changelog: November 11, 2024](https://docs.vapi.ai/changelog/2024/11/11)

[ { "name": "Number of Concurrent Calls", "timeRange": { "start": "2025-12-07T09:34:36.000Z", "end": "2025-12-07T09:39:49.000Z", "step": "minute", "timezone": "UTC" }, "result": [ { "date": "2025-12-07T09:34:00.000Z", "concurrency": 1 }, { "date": "2025-12-07T09:35:00.000Z", "concurrency": 7 }, { "date": "2025-12-07T09:36:00.000Z", "concurrency": 10 }, { "date": "2025-12-07T09:37:00.000Z", "concurrency": 10 }, { "date": "2025-12-07T09:38:00.000Z", "concurrency": 10 }, { "date": "2025-12-07T09:39:00.000Z", "concurrency": 10 } ] } ] analytics endpoint reponse is this during that time but this is incorrect

This Issue might be sitting on the side of your Voip provider as it looks like a CPS (Calls Per Second) limit kicked in, so despite you have enough concurrent channels calls might be rejected by the CPS limitation As example at didlogic we give generous CPS limits from the start to avoid calls failure. Happy to arrange for you @heisenberg 🙂

Thanks for the message, we take that into consideration and setup a delay!

Hi Saikiran, let me reset your concurrency issue.

Hi @Praveen , We have face this issue today afternoon as well, Can you please check into this? seems like we have lot of customers at stake, onto this. @User

Hi saikiran, It seems that your concurrency issues might be related to a problem with the number of calls exceeding your account's limit or potentially a CPS (Calls Per Second) restriction from your VoIP provider. Here are a few steps to consider: 1. **Concurrency Limit Check**: Verify your current concurrency limits by going to the [Settings → Billing](https://dashboard.vapi.ai/settings/billing) in your Vapi Dashboard. Compare

concurrencyLimitIncluded

and

concurrencyLimitPurchased

values to ensure they meet your needs. 2. **Check for VoIP Provider CPS Limitations**: If your concurrency within Vapi is configured correctly, consider checking with your VoIP provider to see if there's a CPS limit that's being reached, causing call rejections. 3. **Analytics Review**: Your provided analytics data shows concurrency at 10 during the error period. It’s worth ensuring that calls are being ended correctly from your side and that these 'active' calls aren't stuck due to unclosed connections. 4. **Logs Review**: Look into your server logs to ensure all

end-of-call-report

webhooks from Vapi are being successfully received and processed. This ensures channels are freed up immediately after a call ends. 5. **Recent Updates**: If there have been any recent updates, as mentioned in the [changelog](https://docs.vapi.ai/changelog/2024/11/11), these might be causing unexpected changes in how concurrency limits are handled. Ensure your systems are ready to handle the load, and do check with your VoIP provider about any limitations they might impose independently from Vapi. If issues persist, consider increasing your concurrency limits or consult with your provider for any other restrictions in place.