Hope all is well, we are experiencing some trouble on the vapi side where we are receiving repeated 429s indicating rate limits, however based on our call volume we shouldn't be hitting these as our limit is at 35 concurrent calls. See here some examples from twilio These calls are not appearing in vapi logs unfortunately and I can not see anything on the platform related to rate limits. Please let me know how we could resolve this issue. The most recent rate limited call is at 2:21 eastern https://cdn.discordapp.com/attachments/1499478274370441226/1499478275456761856/Screenshot_2026-04-30_at_2.14.28_PM.png?ex=69f4f177&is=69f39ff7&hm=00b49e8fe5c86b33d734058ff864697a58055d74c1c1f9ebdc0c7199a45beb1a&

Hey! Looking at your Twilio logs, these are actually 11200 - HTTP retrieval failures, meaning Twilio is trying to hit your VAPI webhook URL but can't reach it — that's likely what's triggering the 429s downstream. This points to VAPI's webhook endpoint being unreachable or timing out, not necessarily a concurrency limit issue. I can help trace the exact failure point. Can you share the webhook URL VAPI is using + any recent changes to your assistant config? @rod007vrr

Hi there, Thanks for reaching out and sharing those details from Twilio. We’ve investigated this and have increased your rate limit to 1000 requests per minute on our end. This should provide plenty of headroom for your current call volume and prevent those 429 errors from occurring. Please let us know if you are still experiencing any issues or seeing rate limits on your side after this change! Best, Vapi Support