Skip to contentSkip to navigationSkip to topbar
Rate this page:
On this page

Guide to Scaling Applications



This documentation is for reference only. We are no longer onboarding new customers to Programmable Video. Existing customers can continue to use the product until December 5, 2026(link takes you to an external page).

We recommend migrating your application to the API provided by our preferred video partner, Zoom. We've prepared this migration guide(link takes you to an external page) to assist you in minimizing any service disruption.


overview page anchor

This section describes some implementation considerations for your video application to allow it to scale efficiently with Twilio; the account quotas are in place to help protect the Twilio Video platform from unnecessarily created Rooms through things like runaway processes, not to hinder your application from expanding. The Twilio Video platform is designed to scale with you as you grow.

When designing your video application for scale it is important to consider the efficient use of resources. The Twilio Video product has some preset Room and participant quotas on each account when it is created. In general these quotas can be updated to ensure there is plenty of room for your application to grow. The default quotas are documented here.

The concurrent Room and participant quotas as well as the request rate quotas are specific to each individual account SID, meaning that they are not shared with subaccounts(link takes you to an external page). All of these quotas can be increased by talking to sales(link takes you to an external page). The following are some additional considerations and troubleshooting steps.

Concurrency Quota Considerations

concurrency-quota-considerations page anchor

There are two dimensions to consider when looking at concurrency:

  1. The number of Rooms that are simultaneously in place to hold users of your application.
  2. The total number of users that can be using your application at the same time; this is measured as the concurrent participants.

There are some considerations that could help your application better fit into these account quotas.

Concurrent Rooms

  1. Consider looking over how many Rooms are being created, especially compared to that of the number of concurrent participants. If you are hitting the concurrent Rooms quota before the concurrent participant quota, then you are likely creating more Rooms than needed. Using Ad-hoc Rooms is a good way to solve this, since it only makes a Room when a participant is trying to join.
  2. Rooms created via the REST API are automatically closed after 5 minutes of having no participants inside of them; this ensures Twilio cleans up open Rooms to not hit this limit as easily. Consider closing Rooms immediately after all participants leave to help eliminate unnecessary Rooms; this could be done by using Ad-hoc Rooms instead of creating them through the REST API.
  3. Talk to sales(link takes you to an external page) if this quota still needs to be increased.

Concurrent Participants

  1. Concurrent participants is the number of participants that are connected in all Rooms in an account at any one point in time. Therefore the total number of people attending an event may not be equal to the peak concurrent participants, as participants may be leaving the event early or joining late. Do consider this when requesting an increase to the concurrent participant quota.
  2. Talk to sales(link takes you to an external page) if this quota needs to be increased.

When approaching either of these concurrency quotas, there will be a 53121 warning that will show up in the Twilio Console when you have reached 70% of your concurrency quota. If you would like an email or webhook alert when this warning is fired, then see this article on creating alert triggers.(link takes you to an external page) Applications should be set up to receive this and notify the developer to take one of the steps above before they receive a 53119 error (for Room concurrency) or a 53206 error (for participant concurrency).

REST API Request Quota Considerations

rest-api-request-quota-considerations page anchor

Read Requests

  1. Implementing StatusCallbacks for different events will decrease the number of REST API requests needed as Twilio will automatically send the corresponding events as they occur. See this documentation on Avoiding Unnecessary Fetching to learn more.
  2. Talk to sales(link takes you to an external page) if this quota still needs to be increased.

Write Requests

  1. If you are creating Rooms through the REST API, then using Ad-hoc Rooms can decrease the number of Write requests that you are making to the Video service.
  2. Talk to sales(link takes you to an external page) if this quota still needs to be increased.

If you are using multiple Twilio products and run into a 20429 error, the first step is to be sure that you are hitting the concurrency quota of the Twilio Video and not the API concurrency limit of the Twilio platform; when just using the Video product, you will run into the product's requests per second quota before you run into the platform concurrency limit. In either case, rely on callbacks instead of unnecessarily fetching data using the API, as well as implementing retries with exponential backoff; both of these methods are detailed in this support article.(link takes you to an external page)

Rate this page: