11-16-2025, 04:35 PM
Ahoy!
You’re receiving this email from Twilio because you’ve used Programmable Messaging and experienced more than 5000 message failures or had messaging failures making up more than 5% of your traffic in the past 30 days.
Effective September 30, 2024, Twilio will begin billing for failed messages in Programmable Messaging. As part of our commitment to transparency and improving message deliverability, we have introduced new features that provide detailed insights into message delivery errors and how to address them. With these enhancements, a failed message processing fee of $0.001 will be applied to messages that terminate in a "Failed" status. This does not affect messages that end in any other status.
Please note that you will not be billed for:
You will never be billed for errors that are Twilio internal issues, or linked to other products or features.
Twilio conducts pre-checks to help you avoid standard termination costs incurred by most CPaaS providers. Processing failures incurs costs for us, and this new fee will help us maintain and improve our services sustainably.
Review your account’s failed message volume in the Messaging Insights dashboard in Twilio Console to better understand your Twilio integration’s health and the impact of this change. If you see a high rate of message failures, use the messaging insights tool to explore their common error codes and causes. For the vast majority of customers, this change will change your bill by less than 1%.
Common causes for elevated error rates include:
Team Twilio
Effective September 30, 2024, Twilio will begin billing for failed messages in Programmable Messaging. As part of our commitment to transparency and improving message deliverability, we have introduced new features that provide detailed insights into message delivery errors and how to address them. With these enhancements, a failed message processing fee of $0.001 will be applied to messages that terminate in a "Failed" status. This does not affect messages that end in any other status.
Please note that you will not be billed for:
- Failures due to Twilio internal errors (Error codes 12400, 20500, 20504, 30103, 30500, 63010, 63012)
- Failures due to Twilio account suspension or Twilio imposed trial and fraud detection limits (Error codes 30002, 30454, 63038, 90010)
- Messages that are failed by SMS Pumping Protection (Error code 30450).
- Meta imposed WhatsApp restrictions beyond a customer’s ability to remedy (Error codes: 63013, 63018, 63021, 63024, 63032).
You will never be billed for errors that are Twilio internal issues, or linked to other products or features.
Twilio conducts pre-checks to help you avoid standard termination costs incurred by most CPaaS providers. Processing failures incurs costs for us, and this new fee will help us maintain and improve our services sustainably.
Review your account’s failed message volume in the Messaging Insights dashboard in Twilio Console to better understand your Twilio integration’s health and the impact of this change. If you see a high rate of message failures, use the messaging insights tool to explore their common error codes and causes. For the vast majority of customers, this change will change your bill by less than 1%.
Common causes for elevated error rates include:
- Retrying requests to create messages when Twilio’s API responds with a 4xx HTTP status code.
- Invalid numbers in your contact lists. If you see numbers continuing to fail with 21211 or 21614 (invalid destination address) or 21610 (unsubscribed recipient), you should update or remove those numbers from your contact lists.
- A cause associated with another particular error code. In insights, you can review your common error codes. Each error code has an entry in our error dictionary with possible causes and solutions.
Team Twilio
Gabriel
Technical Analyst I
WHMCS Services
Technical Analyst I
WHMCS Services