Skip to content
A2PCheck

Twilio Error 30005: Unknown Destination Handset

Error 30005 means the destination number is unknown or no longer in service — the carrier doesn't recognize it.

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 30005 means

The destination number is unknown and may no longer exist. Twilio receives this status from carrier partners and returns it to you.

Official Twilio name: 30005: Unknown Destination Handset

Why error 30005 happens

The number is disconnected or was never valid, is in the wrong format, can't receive SMS (landline), or the device is off with poor signal. Unlike 30003, 30005 more often points to a genuinely bad or dead number.

How to fix error 30005

  1. Confirm the number is in correct E.164 format with the right country code.
  2. Resend once via the API to verify the failure persists rather than being transient.
  3. Use Lookup to validate the number and line type before re-sending.
  4. Remove numbers that consistently return 30005 from your sending list — they're likely dead.
  5. Collect three recent Message SIDs and contact Twilio Support if valid numbers keep failing.

Related error codes

Twilio error 30003: Unreachable Destination HandsetDelivery & handset failuresTwilio error 30006: Landline or Unreachable CarrierDelivery & handset failuresTwilio error 30004: Message BlockedCarrier filtering & content blocks

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 30005 documentation

Frequently asked questions

What's the difference between 30003 and 30005?

30003 (unreachable) is usually temporary — the phone is off or out of coverage. 30005 (unknown handset) points to a number the carrier doesn't recognize, often disconnected or invalid. 30003 is worth retrying; 30005 usually isn't.

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