Skip to main content
All CollectionsFAQ & TroubleshootingRing.io SMS Errors
Why are my text messages not being delivered?
Why are my text messages not being delivered?
Sam Aparicio avatar
Written by Sam Aparicio
Updated over a week ago

Ring.io Business SMS supports the sending and receiving of messages from wireless and wireline numbers. This simply means that you can send and receive messages along with multimedia messages (images) to anyone that uses a mobile device or a service such as Google Voice.

If your messages are not being delivered, this will be indicated by a Red Exclamation Bubble next to the timestamp of the message. Hover your cursor over the bubble and an error code will be displayed.

Curious to know what each error code means? We've put together a handy chart of the common error codes if a message fails to be delivered. Error code not on the list? Well, you can always use the most powerful search engine in the world to look up the error code or you can email our team at support@ringio.com.

Error Code

Cause

ERROR - 30003

The destination handset you are trying to reach is switched off or otherwise unavailable. This likely indicates you're attempting to send the message to a landline. Come on, who uses a landline these day?!

ERROR - 30004

Your message was blocked. The destination number you are trying to reach is blocked from receiving this message.

ERROR - 30005

The destination number you are trying to reach is unknown and may no longer exist.

ERROR - 30006

Landline or unreachable carrier

ERROR - 30007

Message was filtered or blocked. Please confirm you have completed the SMS campaign form or verify your message does not go against carrier guidelines.

ERROR - 30008

If a message you sent is not delivered to the end device and returns a 30008 error code, this means that delivery of your message failed for unknown reasons.

When Twilio receives a very generic error from our carrier partner that we have no further details about, we associate the message with the error code 30008, letting you know that Twilio truly doesn’t know what caused this error from the provider.

Did this answer your question?