30003: Unreachable destination handset
MESSAGING
ERROR
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 recipient device is powered off or otherwise unavailable.
- The device has insufficient signal or is roaming off-network, so the carrier cannot reach it.
- The destination number cannot receive SMS, such as a landline or another unsupported line type.
- A downstream carrier or mobile network issue is preventing delivery to the handset.
- If you send from a short code, the recipient's wireless plan may not support short code messaging.
- If you send from a long code or toll-free number, repeated failures can also indicate carrier-side filtering or blocking.
- Retry the message with another test send through the REST API. A one-time downstream issue can cause a transient delivery failure.
- Confirm that the destination device is powered on and has usable signal. If signal is weak, have the recipient reconnect to the network and try again.
- Confirm that the device is connected to its home carrier network. Twilio cannot guarantee delivery to devices roaming off-network or internationally.
- Ask the recipient to test whether the device can receive non-Twilio SMS. This helps confirm whether the handset can receive messages from other senders.
- Ask the recipient to test messages from another Twilio number or with a shorter one-segment body. This can help isolate sender type or content-related delivery issues.
- 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 short code failures, confirm that the recipient's wireless plan supports short code messaging. If it does not, the recipient may need to contact their carrier.
- For repeated long code or toll-free failures, review your sender type, use case, and content for filtering risk. Approved sender types and compliant traffic can improve delivery in supported markets.
- If the issue continues, collect at least three recent Message SIDs that failed with 30003 and contact support for investigation.