SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

How Fast Can I Place or Receive Phone Calls with Twilio?

Question 

How fast can I place or receive phone calls with Twilio?

 

Product

Programmable Voice 

 

Environment

legacy Twilio Console

 

Answer

There are some limitations to the number of simultaneous inbound and outbound calls that can be placed and received using Twilio's Programmable Voice, Client, and Elastic SIP Trunking products. This guide explains the restrictions for these products.

 

Call Concurrency Limitations

Call concurrency refers to the total number of active, simultaneous voice calls — both incoming and outgoing — operating on an account at any given moment. Unlike Calls Per Second (CPS), which limits the rate of starting calls, concurrency measures the total volume of ongoing conversations.

*NOTE: Our Call Concurrency Limitations have recently changed. Accounts upgraded from trial on or after February 3rd, 2026 will require an approved Business Primary Customer Profile (PCP) for unlimited call concurrency. Newly upgraded accounts with an approved Individual PCP will be limited to 3 concurrent calls. Accounts upgraded prior to February 3rd, 2026 are unaffected at this time. 

Account Type

Programmable Voice Call Concurrency Limit

Elastic SIP Trunking Call Concurrency Limit

Trial

5

4

No Approved PCP

2

2

Approved Individual PCP

3

3

Approved Business PCP

Unlimited

Unlimited

 

Outbound SIP and API Calls (Calls per Second - CPS)

By default, each Twilio account can make 1 outgoing call per-second (CPS). This rate limit applies to both Outbound API-requested Programmable Voice calls, and Elastic SIP Trunking calls. You can have as many concurrent calls as your servers will allow (with an approved Customer Profile), but calls can only be placed at the rate of one per second.

Notice: API requests for calls that exceed the CPS rate limit will be queued, and executed as capacity is available.  Calls that exceed 24 hours in the queue will be cancelled. Exceeding the CPS rate on an Elastic SIP Trunk will result in a failed call with a SIP 503 Trunk CPS limit exceeded response.

Notice: In aggregate calls are executed at the rate defined by the CPS. Individual calls may not execute at the anticipated rate — you may see individual seconds with more or fewer CPS, especially for bursty traffic — but over a month the call execution rate will average the CPS rate set for that account or trunk.

If your project requires additional outbound call throughput, you can increase your CPS limit from Twilio Console:

Note: Currently, the self-serve option for increasing CPS is only available to customers with an approved Business PCP . If you have an Individual PCP, your Twilio Account's CPS shall remain at 1.  

 

Outbound <Dial> calls

There is no rate limit for outgoing <Dial> calls for forwarding, conferencing, or Client (with an approved Business PCP ). That said, there are limitations at the destination for these calls:

  • Twilio <Dial> forwarding to another phone number limitations depend on the destination phone number. Calls exceeding the limit may not connect or be marked busy.
  • Twilio <Conference> has a maximum limitation of 250 participants, but rooms can be configured to have a lower maximum. 
  • Twilio <Client> calls forwarded to a user who is already connected will fail with a SIP 486 Busy here response.
  • Twilio <Client> calls toward an endpoint that is not registered/online will result in SIP 410 Gone response.

 

Incoming calls

Twilio places no limitations on the rate at which projects can receive inbound calls (with an approved Business PCP ). Every incoming call received at your Twilio phone number corresponds to an HTTP request we submit to your webhook / request URL or SIP Trunk Origination URI. We recommend users make sure your server is capable of handling the load if you are expecting a large amount of concurrent inbound traffic.

Have more questions? Submit a request
Powered by Zendesk