Skip to content
A2PCheck

Twilio Error 30003: Unreachable Destination Handset

Error 30003 means the destination handset was unreachable — usually powered off, out of service, or unable to receive SMS at that moment.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

What Twilio error 30003 means

The destination handset is unavailable on the carrier network. This usually happens when the device is powered off, has no service, cannot receive SMS, or is otherwise temporarily unreachable.

Official Twilio name: 30003: Unreachable Destination Handset

Why error 30003 happens

The recipient's device is off or has no signal, is roaming off-network, or the number can't receive SMS (landline or unsupported type). Persistent 30003 to many recipients can also hint at carrier filtering of your sender or content.

How to fix error 30003

  1. Retry the message later to rule out a transient outage.
  2. Confirm the recipient's device is powered on with signal and can receive SMS from other senders.
  3. Use Lookup Line Type Intelligence to confirm numbers are SMS-capable before sending.
  4. If many recipients fail at once, review your sender type and content for carrier-filtering risk.
  5. Collect at least three failed Message SIDs and contact Twilio Support if the pattern persists.

Related error codes

Twilio error 30005: Unknown Destination HandsetDelivery & handset failuresTwilio error 30006: Landline or Unreachable CarrierDelivery & handset failuresTwilio error 30008: Unknown ErrorDelivery & handset failures

Official reference

For the authoritative definition and any changes to this code, see the Twilioerror catalog. A2PCheck is an independent pre-scan layer for the campaign packet you submit — it can't change carrier behavior.

Twilio error 30003 documentation

Frequently asked questions

Is 30003 permanent?

Usually not. 30003 is typically transient — the handset was off or out of coverage. A single retry later often succeeds. If it fails repeatedly across many recipients, look at line type (Lookup) and possible carrier filtering of your traffic.

Free — no signup required

Catch the campaign issue behind this error before you resend

Many of these errors trace back to an unregistered, mis-scoped, or non-compliant A2P 10DLC campaign. Paste your campaign details for a free readiness scan — no signup.

Independent pre-submission check
No Twilio or TCR submission
Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

01

Campaign Info

Basic details about your messaging campaign.

0 characters — Too short — describe who opts in, what you send, and how often.

02

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages
03

Opt-In / Message Flow

How users consent to receive your messages.

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

  • Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
  • Spell out the consent language — what the subscriber explicitly agrees to.
  • State the message frequency (e.g. recurring, varies, msgs/month).
  • Include a "Message and data rates may apply" disclosure.
  • Link a privacy policy describing how you handle subscriber data.
  • Clarify that consent isn't a condition of purchase, where that applies.
  • Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan
Scan my campaign for this issueAll A2P 10DLC error codes