Twilio

Twilio Error 21408

Twilio Error 21408 means SMS Geo Permissions block your destination country. Enable the region in Console > Messaging > Settings > Geo Permissions to fix it.

Updated Jul 1, 2026

The short answer

Twilio Error 21408 ("Message blocked: permissions disabled for the destination region") usually means your account tried to send an SMS to a country disabled in Messaging Geo Permissions; new accounts can message only their verified home country. It can also fire when the destination is not supported for your channel or is blocked by regulation, which Geo Permissions cannot fix. For the Geo Permissions case, enable the country under Console > Messaging > Settings > Geo Permissions; changes take effect immediately.

Twilio returns error 21408 with the message "Message blocked: permissions disabled for the destination region." In most cases this is a Geo Permissions block: your account is not currently allowed to send SMS to the country the To number belongs to. But the same error code can also fire when the destination isn't supported for the channel you're sending on, or when the destination is blocked by regulation — neither of which Geo Permissions can fix.

What causes Twilio Error 21408?

Twilio's Messaging Geo Permissions gate outbound SMS by destination country so accounts don't incur unexpected charges or fraud exposure in regions they don't operate in. Error 21408 fires when:

  • The destination country is disabled in your account's SMS Geo Permissions.
  • Your account is new. By default a new account can only message the home country verified at signup until you enable additional destinations.
  • The To number has the wrong country code. Geo Permissions are evaluated by destination country code, so a malformed or mis-prefixed number can resolve to a country you have not enabled.
  • A subaccount inherits a restrictive parent setting, or the parent's permissions changed.
  • Your channel doesn't support the destination. For WhatsApp and RCS, Twilio blocks certain destinations (for example, numbers starting with +98) regardless of your Geo Permissions settings — there is no toggle to enable these.

Note that some destinations are blocked by regulation and cannot be enabled via Geo Permissions at all (Twilio halted traffic to Iran, and later Syria and Cuba) — those produce related blocks you cannot toggle off.

How do I fix Twilio Error 21408?

The steps below fix the Geo Permissions case, which is the most common cause. If your destination is unsupported for the channel (WhatsApp/RCS) or blocked by regulation, there is no Console setting that will resolve it — you'll need to use a supported channel or destination instead.

  1. In the Twilio Console, go to Messaging > Settings > Geo Permissions (SMS Geo Permissions).
  2. Find the destination country using the filter or continent list, and check the box next to it to enable it.
  3. If the country is flagged High Risk for SMS fraud, you must also tick the acknowledgement confirming you accept the added risk and financial exposure.
  4. Click Save geo permissions and confirm. Changes take effect immediately, so you can retry the send right away.

A few important details:

  • Only Account Owner and Account Admin users can change Geo Permissions, and there is no API to change them — it must be done in the Console.
  • Subaccounts inherit the parent account's permissions by default; if you use subaccounts, verify the setting on the account actually sending the message.
  • Before enabling a new country, confirm the To number's country code is correct (E.164 format). If the number is wrong, fixing the number — not the permission — is the real fix.

Reference: Twilio Error 21408.

FAQ

Common questions

New Twilio accounts can only send SMS to the home country verified during signup. Every other destination is disabled in Geo Permissions until you explicitly enable it under Console > Messaging > Settings > Geo Permissions.

One API, every provider

Stop debugging raw provider errors

Courier connects to your email, SMS, and push providers, handles retries and failover, and surfaces delivery errors in plain language.

Last reviewed Jul 1, 2026. Courier is not affiliated with third-party providers; error behavior may vary by implementation.