Twilio error 13225 means the destination phone number in your Dial verb has been identified as a forbidden destination that Twilio will not connect under any circumstances from your account's current configuration. Forbidden numbers include premium rate numbers, certain international ranges associated with toll fraud, numbers in OFAC-sanctioned countries, and numbers in geographic regions your account has not been authorized to dial. This is a hard block that cannot be overridden by changing your TwiML or account settings alone.
What Causes This Error
Premium rate numbers, such as 900 numbers in the US, 09x numbers in the UK, and equivalent high-cost ranges in other countries, are blocked by Twilio by default to prevent toll fraud and unexpected billing charges on customer accounts. Numbers in countries subject to OFAC (Office of Foreign Assets Control) sanctions, including certain regions of Russia, Iran, North Korea, Syria, and Cuba, are blocked at the platform level regardless of account permissions and cannot be enabled. International geographic ranges associated with known toll fraud schemes, such as certain Caribbean and Pacific island number ranges (country codes +267, +268, +676, and others historically used in international revenue sharing fraud) are blocked preemptively. Dialing emergency services numbers (911 in the US, 999 in the UK, 112 in Europe) from a Twilio Dial verb is also forbidden, as these require special carrier routing that Twilio does not support through the standard TwiML Dial mechanism.
How to Fix It Step by Step
Open the Twilio Console and navigate to Monitor, then Debugger to find the 13225 error entry, which includes the specific forbidden number that triggered the block. Look up the destination number's country code and number range against Twilio's published list of restricted destinations in the documentation under Voice Geographic Permissions to understand which restriction category applies. If the destination is a premium rate number that your business legitimately needs to call (for example, a customer service line that happens to be a premium rate number), contact Twilio support to request a specific exception for that number range, which may be granted for documented business purposes. If the destination is a result of user-provided input (for example, a user entering a number to be called back), your application should validate the number against known forbidden ranges using a number intelligence service before passing it to your TwiML Dial verb.
How to Prevent It from Recurring
Implement a destination number pre-validation layer in your application that checks numbers against Twilio's forbidden categories using the Lookup API with type=line_type_intelligence before constructing the Dial TwiML, and rejects or flags numbers that belong to premium rate or toll fraud-associated ranges. Maintain an application-level blocklist of number prefixes associated with known forbidden categories (900+, certain Caribbean country codes, satellite number ranges starting with +870, +881, +882) and filter these out at the point of user input, returning a clear error message to users who attempt to call these numbers. Enable geographic permissions only for countries your business legitimately needs to call, using the Conservative or Standard dialing permissions tier in Console, then Settings, then Voice Geographic Permissions, which blocks the highest-risk international ranges by default. Add monitoring on your application's call destination data to flag any unusual patterns such as a sudden increase in calls to high-cost international ranges, which may indicate account compromise or a user exploiting your call-back feature.
When to Call a Specialist
If 13225 errors are appearing on numbers that are not in any known forbidden category and that your business has dialed successfully in the past, Twilio may have updated its forbidden list to include a new range that previously was not blocked, and a specialist can investigate whether the block is intentional and whether an exception request is appropriate. A specialist is essential if your business model requires dialing number ranges that are on Twilio's default forbidden list, as exception requests require business justification documentation and a clear explanation of the use case that will be more compelling with professional preparation. You should also seek specialist help if 13225 errors are appearing on numbers from countries that are fully enabled in your geographic permissions settings, as this discrepancy may indicate a routing configuration issue rather than a true forbidden number block.
Conclusion
Error 13225 is a hard destination block that requires either removing the forbidden number from your dial attempts or filing a justified exception request with Twilio for legitimate business-critical destinations. 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.