Twilio error 30022 means your A2P 10DLC campaign has exceeded the throughput rate that the carriers have approved for your specific campaign registration. A2P 10DLC campaigns are approved at a messages-per-second rate that is tied to your brand type, campaign use case, and monthly message volume declaration, and 30022 fires when your actual send rate exceeds that approved ceiling. This is not an account-level throttle but a campaign-level enforcement by the carriers, and raising the limit requires action through the TCR registration system.
What Causes This Error
Standard A2P 10DLC brands are typically approved for between 4.5 MPS and 15 MPS depending on the use case and carrier, while unvetted brands start as low as 1 MPS on T-Mobile. Sending a large batch of messages in a tight window without spreading the send across multiple numbers in your pool is the most common trigger for 30022, because all the traffic is being counted against the campaign's aggregate throughput limit. An underestimated volume declaration in your original TCR campaign registration is a second cause: if you declared 10,000 messages per month during registration but are actually sending 100,000, the per-second rate limit set by the carriers at registration time will be too low for your actual volume. Using a single sending number instead of a Twilio Messaging Service number pool is a third cause, as a single number is constrained to far lower throughput than a number pool operating under the same campaign.
How to Fix It Step by Step
Go to the Twilio Console, navigate to Messaging, then Senders, and find your A2P campaign registration. Check the current approved throughput per carrier listed on the campaign detail page and compare it to your measured send rate from your application logs. If you need higher throughput, click through to your TCR profile and submit a throughput increase request, which requires updated monthly volume figures and sometimes a manual carrier review that can take 5 to 10 business days. While you wait for the increase to be approved, reduce your send rate immediately by adding inter-message delays in your queue processor to stay within the currently approved MPS rate and stop generating 30022 errors.
How to Prevent It from Recurring
Use a Twilio Messaging Service configured with a pool of at least 5 to 10 long code numbers assigned to the same 10DLC campaign: the Messaging Service distributes sends across the number pool, which multiplies your effective throughput while keeping each individual number within its carrier-approved rate. Calculate the exact MPS you need for each campaign before registering by dividing your peak hourly message volume by 3600 seconds and adding a 30 percent buffer, then declare this rate in your TCR application to ensure the approved rate covers your needs from day one. Monitor your send rate per campaign in real time by building a metrics dashboard that tracks messages sent per second per campaign ID, and configure an alert when the rate approaches 80 percent of your approved MPS ceiling. Review your TCR campaign registrations quarterly and update your volume declarations if your business has grown, as carriers do audit declared versus actual volume over time.
When to Call a Specialist
TCR throughput increase requests that are pending review for more than 10 business days often require a specialist to follow up directly with Twilio's carrier relations team, as these requests can stall in the review queue without proactive advocacy. If you have a legitimate high-volume use case (over 500,000 messages per day from a single campaign) and standard 10DLC throughput is not sufficient, a specialist can advise on whether a dedicated short code would be a better fit and manage the provisioning process. You should also escalate if you are seeing 30022 errors on a campaign that was previously delivering at the same rate without errors, as this may indicate a retroactive downgrade of your campaign's approved throughput by a carrier. Throughput registration gaps during high-volume campaigns cause message loss that is not recoverable after the send window closes.
Conclusion
Error 30022 is a campaign throughput ceiling that is raised through TCR, not through Twilio alone, and the process takes time to complete correctly. If this error is blocking your production system, contact our team and we will diagnose and fix it within the hour.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.