If a message you sent is in the "undelivered" status, this means that delivery of your message failed after Twilio sent the message to the carrier. Twilio displays the 30008 error code when we receive a generic error from our carrier partner, or when the error code Twilio received has not yet been matched to one of the other Twilio error codes in the 30000 series.
If the message you sent has a "failed" status with error 30008, this means Twilio encountered an error while processing the message. For more information about possible message statuses, see What are the Possible SMS and MMS Message Statuses, and What do They Mean?
See below for further troubleshooting steps for different error 30008 situations.
"Undelivered" messages with error 30008
In some cases a delivery error may occur once due to a transient issue downstream of Twilio. To test whether the issue occurs again, you can attempt to send another message to the user via a REST API request, or through the API Explorer in Console.
If you see similar results, continue troubleshooting with the following checklist:
- Check the Twilio Status Page to see if an active incident could be causing your issues.
- Is the destination device powered on?
- Does the device have sufficient signal? If not power the device off, wait 30 seconds, and then power it back up.
- Is the device connected to the home carrier's network? We cannot guarantee message delivery on devices roaming off-network.
- Can the device receive non-Twilio SMS?
- Can the device receive messages from another Twilio number (non-Alphanumeric Sender ID), or with a shorter one-segment (non-concatenated) body?
- Can other devices using the same mobile carrier receive your messages?
"Failed" messages with error 30008
First, check whether the message with this error was an MMS (media message) or an SMS. "Failed" messages with error 30008 are most common when attempting to send MMS messages.
Failed MMS messages with error 30008
This error may occur because the Media URL you provided is not reachable when Twilio tries to retrieve the media. It may also occur because the Content-Type header on the media object does not match the file extension. Please try the following troubleshooting steps:
- Ensure the Media URL provided is accessible on the public Internet – Twilio cannot retrieve media from URLs that require authentication
- Ensure that the Content-Type header for your media URL matches the file extension. For example, if your file has the extension .jpg, but the Content-Type header is image/png, you must verify what the actual file format is and ensure both of these properties match the actual file type.
Failed SMS messages with error 30008
SMS that are "failed" (instead of "undelivered") with error 30008 are very uncommon, and may be the result of a temporary outage or issue on Twilio's platform. Check the Twilio Status Page to see if an active incident could be causing your issues.
Continued Error 30008 Issues
If you can rule out all of the above issues, Twilio's Support team can help investigate what went wrong with delivering your message. Please collect 3 or more Message SIDs in your SMS logs from the last 24 hours that were flagged with Error 30008, and Open a support request.