Skip to content
A2PCheck

Twilio Error 30006: Landline or Unreachable Carrier

Error 30006 means the destination can't receive your message — typically a landline, or a short code that couldn't reach the destination carrier.

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

The destination number cannot receive your message. Twilio returns 30006 when the destination is a landline, or when a short code cannot reach the destination carrier.

Official Twilio name: 30006: Landline or Unreachable Carrier

Why error 30006 happens

The recipient number is a landline (which can't receive SMS), the line type is incompatible with SMS, or a short code has no route to that particular carrier. It's a capability/routing mismatch, not a content problem.

How to fix error 30006

  1. Use Lookup Line Type Intelligence before sending to confirm the number is mobile and SMS-capable.
  2. Don't retry landline numbers — send to a mobile alternative instead.
  3. Add fallback senders to your Messaging Service so Twilio can switch from a short code to a long code when needed.
  4. Monitor error codes in your StatusCallback handler and prune numbers that consistently return 30006.

Related error codes

Twilio error 30003: Unreachable Destination HandsetDelivery & handset failuresTwilio error 30005: Unknown Destination HandsetDelivery & 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 30006 documentation

Frequently asked questions

Can I fix 30006 by resending?

No — if the destination is a landline it can't receive SMS at all, so retries won't help. Screen numbers with Lookup Line Type Intelligence before sending, and for short-code routing gaps add a long-code fallback sender to your Messaging Service.

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