Hi Roman,
- Purchasing additional reserved concurrency (call lines) increases your allowed simultaneous calls, but it does not automatically bypass Cloudflare rate-limits or DDoS protections. Concurrency controls call slots on Vapi’s side; Cloudflare protection and API request rate limits are separate layers.
- Native auto-scaling of Cloudflare thresholds or per-request API rate limits is not available on the self-serve plan. To get higher API rate limits and relaxed protection settings (and enterprise-grade capacity), you must move to an Enterprise plan — see
https://docs.vapi.ai/enterprise/plans.
- Recommended approach to avoid Cloudflare blocks while staying on the current plan:
1. Buy the necessary Reserved Concurrency lines in the Dashboard:
https://dashboard.vapi.ai/settings/billing (this prevents Vapi-side concurrency blocks).
2. Throttle and batch outbound requests from your side (e.g., smaller batches, paced retries) so request rates hitting Vapi/Cloudflare stay steady rather than spiky.
3. Use exponential backoff on 429s and monitor the
subscriptionLimits
fields returned by
POST /call
to detect approaching capacity (see
https://docs.vapi.ai/calls/call-concurrency).
4. If Cloudflare blocks persist, provide timestamps and example request IDs so we can investigate specific incidents.
- If you need predictable, higher per-second API throughput and control over protection rules, the path is Enterprise — that plan includes higher rate limits and dedicated support to tune protections:
https://docs.vapi.ai/enterprise/plans.