Twilio Errors 30003, 30005, 30006 and 30008 Explained

Updated

Short answer: These four Twilio codes are delivery failures, not registration rejections. 30003 means the phone was unreachable, 30005 means the number is unknown and may no longer exist, 30006 means a landline or a carrier that a short code cannot reach, and 30008 is a generic carrier failure with no detail. Check numbers before you send, retry only where Twilio suggests it, and give Twilio Support at least three Message SIDs if a code keeps coming back.

The four codes at a glance

CodeTwilio titleWhat it meansFirst step
30003"Unreachable destination handset"The phone is off, has no service, cannot receive SMS or is temporarily unreachableRetry once, and check the line type
30005"Unknown destination handset"The number is unknown and may no longer existCheck the number's format
30006"Landline or unreachable carrier"The number is a landline, or a short code cannot reach that carrierDo not retry the same SMS to a landline
30008"Unknown error"A generic failure from a carrier or downstream providerRetry with a shorter, simpler message

30003: Unreachable destination handset

Twilio says: "This error 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."

The number may also be one that cannot take texts: "The destination number cannot receive SMS, such as a landline or another unsupported line type." And when you send from a long code or toll-free number, "repeated failures can also indicate carrier-side filtering or blocking."

What Twilio suggests:

  • "Retry the message with another test send through the REST API. A one-time downstream issue can cause a transient delivery failure."
  • "Verify that the destination number is SMS-capable before sending. Use Lookup Line Type Intelligence to filter out landlines and other unsupported line types."
  • "For repeated long code or toll-free failures, review your sender type, use case, and content for filtering risk."
  • "If the issue continues, collect at least three recent Message SIDs that failed with 30003 and contact support for investigation."

If filtering looks likely, see Twilio error 30007.

30005: Unknown destination handset

Twilio says: "This delivery error indicates that the destination number is unknown and may no longer exist. Twilio receives this status from carrier partners and returns it to you."

Twilio lists four possible causes. The number may no longer exist. The device may be powered off or have too little signal. The number may be a landline. Or "An issue at the mobile carrier is preventing delivery."

Start with the number itself: "Verify the destination number is in proper E.164 format with the correct country code and subscriber number." If the error persists, Twilio asks you to collect at least three recent Message SIDs that show 30005 and open a support ticket.

Deactivated numbers should come off your list. CTIA's Messaging Principles say: "Message Senders should process telephone deactivation files regularly (e.g., daily) and remove any deactivated telephone numbers from any opt-in lists."

30006: Landline or unreachable carrier

Twilio says: "This delivery error 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."

The two cases call for different handling:

  • For a landline: "If Lookup returns landline, do not retry the same SMS to that destination. Send to a mobile number instead."
  • For repeat failures: "Review the ErrorCode in Messaging logs and in your StatusCallback handler so you can identify recurring 30006 failures and remove incompatible destinations from future sends."

30008: Unknown error

Twilio says: "This error means we received a generic delivery failure from a carrier or downstream provider and did not receive enough detail to classify the failure more specifically."

Two of the causes Twilio lists are "The destination handset is off, unavailable, or otherwise unable to receive SMS at the time of delivery." and "Message length, concatenation, or character encoding contributes to the carrier failure."

So Twilio suggests: "Retry with a shorter message body and simple characters to help rule out segmenting or encoding issues." If the problem persists, "open a support request and include at least 3 recent Message SIDs that returned 30008. Provide examples that are no older than 48 hours."

To prepare a shorter, simpler body, you can use Precheckly's free SMS segment calculator. It runs in your browser, shows the encoding and segment count, and highlights characters outside GSM-7.

If you send through HighLevel

HighLevel's LC Phone policy sets Do Not Disturb (DND) on a contact when a message fails with some of these codes:

CodeHighLevel's descriptionWhat HighLevel does
30003"Unreachable — Out of Service""Enable Temporary DND"
30005"User Inactive / Number does not exist""Enable Temporary DND"
30006"Landline / incapable of receiving SMS""Enable Temporary DND"
30008"None of the above scenarios matched""Do nothing"

HighLevel also watches error rates, and it now has two sets of rules. Under the old rules, HighLevel says a high delivery error rate means "you are sending SMS to contacts that are no longer in service, are unreachable, or use a non-SMS-capable device such as a landline", and "Once the error rate hits 10%, the sub-account will be locked for sending text messages for 24 hours." Under the new rules, which HighLevel is rolling out to "a selected group of sub-accounts", "Only messages flagged by downstream providers with error 30007 count toward the carrier filtering rate." See why GoHighLevel paused your SMS for both.

Either way, HighLevel says to "remove invalid numbers, landlines, and prior opt-outs before a bulk send." Its Number Intelligence feature "looks up the number before sending and applies a temporary DND on the contact if it is not SMS-capable."

How to avoid these errors

  • Check the line type before you send, and leave landlines out of SMS sends.
  • Store numbers in E.164 format, with the country code.
  • Process deactivation files and remove deactivated numbers, as CTIA recommends.
  • Track error codes per number in your status callbacks, so repeat failures stand out.
  • When a code keeps coming back, collect at least three recent Message SIDs and contact Twilio Support.

These codes are not about registration. For A2P 10DLC and toll-free problems, see Twilio error 30034, toll-free verification vs A2P 10DLC and the list of A2P 10DLC error codes.

Sources

Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.