Twilio error 30005 means the carrier cannot identify the destination handset for the number you are attempting to reach. Unlike 30003, which is a temporary reachability issue, 30005 typically indicates a more fundamental problem with the number itself, such as it being unassigned, incorrectly formatted, or associated with a ported number whose routing data has not propagated correctly. Resolving 30005 requires verifying the number before attempting any retries.
What Causes This Error
The most common cause is a number that has been formatted incorrectly, missing the country code or using a local format without the E.164 international standard prefix, for example passing 2125551234 instead of +12125551234 for a US number. A second cause is sending to a number that has been recycled by the carrier and reassigned to a new subscriber, but your database still contains the old subscriber's record with that number. Ported numbers in transition can also return 30005 during the porting window, which can last between 4 and 24 hours as carrier routing tables update across the network. Invalid virtual numbers, such as test numbers or numbers generated by apps that do not map to a real mobile subscriber, will also consistently return this error code.
How to Fix It Step by Step
Use the Twilio Lookup API immediately: send a GET request to lookup.twilio.com/v1/PhoneNumbers/{number} with type=carrier appended as a query parameter, and check the carrier field and line_type_intelligence field in the response to confirm the number is valid and belongs to a mobile carrier. If the Lookup API returns a null carrier or a line type of voip or unknown, the number is not a valid mobile destination and should be removed from your send list. Verify that all numbers in your system are stored in E.164 format by running a regex check for the pattern ^+[1-9]d{1,14}$ and correcting any that do not match. For numbers that passed Lookup but still return 30005, wait 24 hours and retry, as recently ported numbers sometimes need time for routing tables to synchronize across all carrier nodes.
How to Prevent It from Recurring
Validate all phone numbers at the point of collection in your application using the Twilio Lookup API before storing them in your database, adding a real-time validation check to your signup or onboarding forms. Implement E.164 normalization in your backend so that numbers are automatically formatted to the correct international standard regardless of how users enter them. Run a list hygiene job against your full contact database on a monthly schedule, using the Lookup API in batch mode to identify and flag numbers with unknown or null carrier data. Remove numbers that have returned 30005 twice in a 30-day period from your active send list automatically, as persistent 30005 errors are a strong signal of a permanently invalid or recycled number.
When to Call a Specialist
If the Lookup API returns valid data for a number but 30005 errors persist, you may be dealing with a carrier routing anomaly that only appears on the outbound path and requires Twilio support to investigate at the network level. A specialist can also help you design a scalable number validation architecture if you are dealing with large contact lists where calling the Lookup API individually for each number is not cost-effective. Escalate immediately if 30005 errors are appearing on numbers that were delivering successfully yesterday, as this pattern can indicate a larger carrier routing problem or an account-level issue affecting your outbound routes. A sudden cluster of 30005 errors on previously valid numbers almost always warrants urgent investigation.
Conclusion
Error 30005 is almost always a data quality or formatting issue that is fully solvable with proper validation upstream. If this error is blocking your production system, contact our team and we will diagnose and fix it within the hour.
Ready to Transform Your Business Communications?
Get a free consultation with our VoIP experts and discover how we can help you save costs, improve efficiency, and scale your business.
Comments (0)
Join the discussion and share your thoughts (AI-moderated for quality)
Be the first to comment
No comments yet. Share your thoughts below.