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.

Advisory: Potential Message Delays During Black Friday/Cyber Monday 2026

Overview

With the U.S. Elections and the retail holidays Black Friday and Cyber Monday coming up Twilio anticipates a significant spike in short code, 10DLC, toll-free, SMS, MMS, and RCS traffic, starting  from November 24, 2026, through November 30, 2026 (BFCM). Specifically, due to supply constraints on the SMS/MMS network in the United States and Canada, customers that send large bursts of SMS/MMS traffic may experience additional delays in deliverability, across all SMS/MMS sender types.

In the event of downstream congestion among network carriers, it is anticipated that short code, 10DLC, and toll-free SMS/MMS traffic may queue for several minutes longer compared to off-peak sending times. If your SMS/MMS traffic is queuing for approximately 30 minutes or more, please follow status.twilio.com for the latest updates on significant degradation. Any temporary measures that Twilio may take in response to traffic spikes and capacity constraints will also be available on the Status Page. 

Potential downstream carrier congestion on SMS/MMS is not anticipated to affect messages sent over RCS, as RCS messages are delivered over the internet.

This guide covers the following topics:
 

 

What You Need to Know

Queue mitigation strategies

While Twilio will partner closely with the carriers to deliver every message as quickly as possible, there are several strategies that you can leverage during Cyber Week to mitigate increased queueing times.

1. Adhere to your provisioned throughput for SMS and MMS

The most effective strategy for reducing queue length during Cyber Week is to send messages to Twilio at or below your provisioned rate limits, for short code, 10DLC, toll-free messages, and RCS. Rate limits, also known as throughput, for SMS/MMS messages are provisioned per-number or at the account-level. The throughput configured on your numbers will dictate the speed at which Twilio will send your messages downstream to the carriers.

By rate limiting traffic on your application to match your configured throughput, you can avoid building up a backlog of messages that are sent to Twilio faster than they can be processed.

2. Use a shorter Validity Period for your time-sensitive messages

If you are using the same number to send messages with mixed use cases, such as one-time passwords and promotional, time-sensitive messages that are sent to Twilio behind a large burst of traffic may functionally expire within the queue.

To prevent messages with a lower latency from becoming stale due to increased queueing times, configure a Validity Period on each message or Messaging Service that reflects the expected delivery window of the message’s use case. For example, an OTP notification should be configured with a low Validity Period of 5 seconds up to no more than 5 minutes, while a higher Validity Period of 1 hour up to 10 hours is more appropriate for promotional traffic that is targeted to a large audience. The default Validity Period for SMS, MMS, and OTT is set to 10 hours if no value is provided.

The Validity Period is only applicable to the Twilio Platform. If traffic congestion is downstream (carriers) the Validity Period will not be applicable.

3. Implement retries with exponential backoff and continuously monitor API usage.

By implementing retries with exponential backoff, you can improve the deliverability of your messages during spikes in traffic. For Black Friday and Cyber Monday, spikes are most often associated with launching marketing campaigns or business news. When sending messages to a large audience, carefully monitor your usage, via API response headers, to ensure that the number of concurrent requests you are making is at parity with your configured concurrency.

Concurrency is defined as the number of concurrent requests per second that can be made towards all endpoints. If you exceed your concurrency limit, you may start to receive 429 “Too Many Requests” error responses, indicating that you are sending more API requests than what Twilio has configured for your account.

During times of increased downstream provider congestion, combining exponential backoff logic with continuous usage monitoring will allow you to more effectively slow requests down. By throttling requests in your application with exponential backoff, downstream queues can be drained with reduced message loss. For instructions on how to implement exponential backoff, you can review our REST API best practices and detailed tips for avoiding 429 error responses.

 

Frequently Asked Questions 

My messages are failing with 4xx or 30001 errors, what’s happening?

These 4xx and 30001 errors typically occur when you continuously send messages at a volume that exceeds your provisioned throughput limits, causing the message queue to fill to capacity. Once your queue reaches its maximum time limit of 10 hours, the Twilio API begins rejecting new requests, resulting in HTTP 429 or 30001 queue overflow errors. To prevent these queuing errors, the most effective strategy is to upgrade your Message Per Second (MPS) throughput limit to properly match your sending volume. For one-time promotional blasts, scheduling or pacing your sends over a longer time window can also stop your traffic from instantly filling the queue. Additionally, adjusting your Validity Period in combination with increased MPS can help you better manage queue times and significantly reduce message failures. 

What’s happening with my messages getting queued on A2P 10DLC? Can I increase my throughput for these messages?

When your A2P 10DLC messages queue, it means your sending volume is exceeding either the maximum MPS granted for your registered Campaign or your overall Account Based Rate Limit (ABRL). Your A2P 10DLC Campaign throughput is determined by your Brand type, Campaign use case, and Trust Score, which dictate the maximum MPS you can send across all major carriers. In addition to specific campaign limits, you must also factor in ABRL, which acts as an overarching account-level ceiling across all of your collective senders. To reduce queueing and increase your throughput, you can move to a higher campaign throughput tier or request an ABRL limit increase to right-size your account for larger volumes. For a comprehensive breakdown of throughput allocation and Trust Scores, please review our help center article on Message throughput (MPS) and Trust Scores for A2P 10DLC in the US. 

Does throughput apply to entire messages, or message segments?

For Twilio’s per-number rate throughput on SMS, throughput is measured in message segments per second (MPS). For MMS, there is no concept of "segments", so MPS is measured in MMS messages per second.

For Account Based Throughput and Market Throughput, a single MPS value is configured for each sender type in the SMS and MMS channels. This means that SMS from short code numbers can share a different MPS than SMS from toll-free numbers. With Account Based Throughput and Market Throughput, customers are given an MPS based on their volume of messages, no matter how many (or how few) senders they have. Although there are no guarantees for downstream capacity, this adds additional predictability for customers managing mixed use case traffic across several number types.

If I have subaccounts, do account-based limits and Market Throughput apply at the subaccount level?

Limits are applied on the parent account level, and include any subaccounts. Subaccounts do not provide any additional throughput.

What happens if I exceed my configured throughput?

If you attempt to send more SMS or MMS messages than can be sent per second based on your configured throughput, the additional messages will be queued in the Twilio platform, and dequeued at the configured MPS. The default maximum queue time is 10 hours. You can specify a shorter queue limit for your messages by setting a different Validity Period value on your Messaging Service or in your API requests.

If you queue up so many messages that you exceed your maximum queue length of 10 hours, the API will start rejecting new requests. If you are not using a Messaging Service, you will observe API errors with HTTP code 429 and error 20429. If you are using a Messaging Service, your message requests will be accepted by the API, but will subsequently fail with Error 30001 - Queue overflow.

For more details on Twilio’s standard sending rate limits and queue behavior, see Understanding Twilio Rate Limits and Message Queues.

Is RCS subject to throughput limitations?

Since RCS uses a distinct Sender type and messages travel over the internet instead of through the carrier infrastructure used for SMS and MMS, the throughput limitations for RCS are managed separately. By default, all RCS Senders have a maximum limit of 100 MPS. Requests to increase the MPS of an RCS Sender must be submitted internally by your AE and must demonstrate a need based on historical volumes. 

Is this throughput guaranteed?

Unless you have implemented one of Twilio’s Traffic Optimization Engine products such as Traffic Shaping or Market Throughput, no - we cannot guarantee throughput. There are ecosystem-wide limitations around throughput capacity, meaning demand could outweigh supply at peak send times. However, these limits improve our predictability, and reduce the risk around provider overflow. Understanding the customer limits allows us to plan for and protect our customers' traffic. Because we can predict the maximum volume of messages we can load test high volumes in advance and we can plan in advance with carriers to ensure we have enough capacity.

If my account is subject to Account Based Throughput, will my 10DLC traffic still be compliant with A2P requirements in the United States?

Yes, A2P 10DLC traffic is subject to Account Based Throughput. However, Account Based Throughput acts as a ceiling for an account, so while it won't affect individual A2P campaign throughputs, it could affect an accounts collective A2P traffic.

With more businesses and organizations utilizing toll-free numbers for A2P messaging, will there be any impact around deliverability for toll-free messages during Black Friday / Cyber Monday?

Twilio works year-round to ensure consistent SMS/MMS deliverability during peak sending hours to help protect our customer’s traffic along with the overall health of our messaging platform. However, when a large portion of our customers send millions to tens-of-millions of messaging traffic over a single channel (toll-free, A2P 10DLC, short code, or RCS) at the same time, there is always a risk in hitting our platform peak. For example, if every Twilio customer attempts to send SMS or MMS messages at 9am EST, that will lead to congestion on our platform and can result in slight delays in each message being delivered. However, even during these peak times of the year like Black Friday/Cyber Monday and peak times of day like the top of each hour, any congestion we see on our platform will resolve itself quickly and typically within the hour. 

To avoid any industry or platform caused messaging delays, we recommend adjusting your messaging sending times and staggering campaigns that are not time-sensitive to be not at the top of the hour.  If you want to prepare even further than adjusting your engagement timing, Twilio offers specialized products such as Market Throughput, Traffic Shaping, and Multi-tenancy to allow for more control over how your traffic is organized, prioritized, and sent with Twilio. These products are available for both Toll-Free and Short Code senders.

What else can we do to prepare for these high-traffic periods?

First and foremost, ensure that you have registered your 10DLC Brands and Campaigns (including adding your phone numbers to the Campaign(s)), verified your Toll-Free numbers, and provisioned any short code numbers at least a week or two before you plan to send the traffic. For customers using short code or Toll-Free numbers, it’s recommended to ensure your desired throughput products are also set up at least a week or two in advance. Customers interested in increased MPS on Toll-Free or short code SMS/MMS can provision the extra capacity using Market Throughput. This allows time for you to test, make changes to workflows and handling, and be best prepared going into these higher volume weeks.

Have more questions? Submit a request
Powered by Zendesk