Twilio errors · 2026
Twilio call blocked: errors 13224, 13225, 21216 and 32017 explained for cold callers
Last updated September 4, 2026
These four codes look alike in the debugger, all say some version of “blocked”, and mean four different things. One is your list. One is your account paperwork. One is Twilio protecting you from a fraud destination. And one, 32017, is the phone network telling you a number has been burned, which no setting fixes. Sorting them out matters because the fix for one is a spreadsheet formula and the fix for another is to stop dialing.
The short answer
13224: fix the number format. 13225 and 21216: fix the account, usually by getting a Business Primary Customer Profile approved in Trust Hub, which is mandatory for +1 calls from any account opened outside the US or Canada since 8 October 2025. 32017: the carrier blocked your caller ID for reputation; register it, rest it, and dial from a fresh number at lower volume.
The four codes side by side
| Code | What it means | Fix | Stop dialing? |
|---|---|---|---|
| 13224 Dial: Twilio does not support calling this number or the number is invalid | The number cannot be routed: malformed, non-existent, premium or shared-cost, or a temporary carrier outage. | Clean the list to E.164 (+14155552671). Skip premium ranges. Retry valid numbers later once. | No |
| 13225 / 21216 Call blocked by Twilio | Twilio refused: fraud-risk destination, regulatory restriction, or the account does not meet the +1 calling requirements (approved Customer Profile; Business profile if the account was created outside the US/Canada on or after 8 Oct 2025). | Trust Hub → Primary Customer Profile → submit or upgrade to Business; wait for approval (up to 48 h). Support cannot override the Business-profile rule. | Until approved |
| 32017 PSTN: carrier blocked call due to calling number (caller ID) | The receiving carrier's analytics engine blocked the call because your caller ID has a poor reputation score: low answer rate, short calls, high unwanted-call volume. | Register the number at freecallerregistry.com and First Orion's portal (T-Mobile). Rest the number. Move the campaign to a fresh number at a lower daily volume. | Yes, on that number |
Meanings and fixes per Twilio's error documentation, read September 2026.
13225 and the October 2025 rule
The cause that catches the most cold callers in 2026 is the third one in Twilio's list. Calls to +1 numbers require an approved Primary Customer Profile on the parent account, and since 8 October 2025 an account created outside the United States or Canada must hold a Business profile: legal business name, physical address, website, an authorised representative, a government ID photo and a selfie, reviewed within up to 48 hours. Twilio's documentation states support cannot remove the block manually. An agent or agency abroad opening its own account will meet this on the first dial; a US-owned account with the agent invited into the dialer does not. Our guide on US numbers for cold calling from abroad walks through the alternatives.
32017 is not a Twilio problem, and Twilio says so
The receiving carriers run analytics engines, Hiya for AT&T, TNS for Verizon, First Orion for T-Mobile, that score every calling number on answer rate, call duration and complaint volume. A number that dials hundreds of short, unanswered calls a day scores badly, first gets labelled “Spam Likely”, and then gets blocked outright, which Twilio reports as 32017. Twilio's own fix list is registration with the engines, via the Free Caller Registry and First Orion's portal, and it notes that going direct is faster than going through Twilio. Registration restores delivery; it does not repair behaviour. Cap each number's daily dials, rotate, and keep calls that connect on the line long enough to count. The mechanics are in fix a Twilio number flagged Spam Likely and calls per day before spam-likely.
13224 is your spreadsheet
A bought list arrives with numbers in six formats: (415) 555-2671, 415.555.2671, 4155552671, 1-415-555-2671, a UK number as 07700 900123, an extension tacked on. Twilio wants +14155552671 and +447700900123. Excel adds insult by dropping the leading + and turning long numbers into 4.15556E+09. Normalise to E.164 before import, dedupe on the normalised value, and drop rows that fail. The remaining 13224s are genuinely dead numbers and premium ranges you should not be dialing anyway. Step by step in how to clean a lead list before you dial it.
Neighbouring codes that are not blocks
- 13227 / 21215: the destination country is switched off in your geo permissions; a one-minute fix. See geo permissions.
- 21210: the caller ID is not a number on your account or a verified caller ID. See error 21210.
- 21219: trial account calling an unverified recipient. See the trial page.
- 21217: the number does not appear valid, the API-side twin of 13224. See error 21217 and list cleaning.
A block is sometimes the right outcome. 32017 on a number that dialed a consumer list 300 times a day without a DNC scrub is the system working. Fix the volume and the list before fixing the label, or the next number goes the same way.
Clean numbers in, the error code on screen when one fails.
DialSheet dials your list on your own Twilio at ~$0.014/min, shows the Twilio code next to the lead when a call is refused, and lets you pin a number per rep so one burned number does not take the team down. Free for one person, $29 per 3 seats. No Twilio? A managed line is $49/month.
Start dialingQuestions people actually ask
What does "13225: Call blocked by Twilio" mean?
Twilio itself, not the carrier, refused to connect the call. Twilio's documentation gives three causes: the destination is flagged as high risk for fraud; a regulatory restriction prevents routing to it; or, for calls to +1 numbers, the account does not meet the requirements, specifically an approved Primary Customer Profile in Trust Hub, and, for accounts created outside the US or Canada on or after 8 October 2025, a Business profile rather than an Individual one. 21216 is the same block reported on a call created through the REST API instead of a Dial verb.
How do I fix "Call blocked by Twilio" for US numbers?
Open Trust Hub in the Console and check the Primary Customer Profile. If there is none, create one and submit it; if the account was created outside the US or Canada after 8 October 2025, it must be a Business profile, which asks for legal name, address, website, an authorised representative, a government ID photo and a selfie. Twilio quotes up to 48 hours for review. Twilio's error page states support cannot remove this restriction manually, so an appeal will not shortcut it. Once the profile is approved, the same numbers connect.
What is Twilio error 32017?
32017 means the call reached the carrier network and an analytics engine on the receiving side blocked it because of the reputation of your caller ID: the number has a low answer rate, generates short calls, or is responsible for a volume of unwanted calls. It is the carrier-side "spam likely" label acting as a block rather than a warning. Twilio's recommended fix is to register the number with the analytics providers directly, via the Free Caller Registry and First Orion's portal for T-Mobile, which Twilio notes is faster than going through Twilio. Then reduce the daily dial count on that number and rotate.
What does 13224 "Twilio does not support calling this number" mean?
The destination cannot be routed or is not a valid callable number. In a cold-calling list the usual causes are formatting (no leading + or country code; a UK number stored with its trunk 0), an area code or subscriber number that does not exist, or a premium-rate or shared-cost number Twilio does not route. Occasionally it is a carrier outage on a valid number, in which case a later retry works. Clean the list to E.164 before dialing and the 13224 rate drops to the genuinely dead numbers.
Is a blocked call charged?
A call refused by Twilio before it leaves (13225, 21216, 13224) is not billed as a connected minute. A 32017 block happens on the carrier side after the call has been placed; check the call record in Console for whether a duration was billed. In a browser dialer the browser leg may bill a minute for the attempt either way.
Should I keep dialing when I see 32017?
No. 32017 is the number's reputation telling you it has been burned. Continuing to dial from it lowers its answer rate further and can drag the reputation of the numbers around it. Stop, register it with the analytics providers, rest it, and move the campaign to a fresh number at a lower daily volume. How many numbers you need for a given dial count is in our guide on calls per day before spam-likely.