Text outage

[jacksonStone]

Looks like it no longer works with Verizon as a carrier.

[jacksonStone]

I only mention that because in your docs, you say it does work with them. I'm really grateful for this free service you've created BTW

[bobmeister9]

I've noticed the same problem. Previously working application stopped working somewhere around April 1. The curl request does return success, but the message is never delivered.

[Techneaux]

Same problem here but seems to be for multiple carriers (tmobile, AT&T, and verizon). Though this is with the textbelt.com hosted version.

[WindfallLabs]

I can second the issues with Verizon and AT&T, and would like to include Sprint PCS. I'm using Python's urllib and urllib2.

[typpo]

Hi guys, I'm aware of an issue but am traveling abroad with very low connectivity (Ethiopia). I won't be able to fix this for at least a few days.

This issue was triggered by someone spamming via Textbelt. The fix is probably to change IP addresses, which I will do ASAP. Another solution would be to use a self-hosted version of Textbelt.

Unfortunately, changing IPs is not a long term solution. This happened in November and will probably happen again. People who abuse the Textbelt service ruin it for others :(

[tankerkiller125]

@typpo I've tried self hosted and dispite having a good email config and what not it still does not send. Possibly change in those Gateways acceptance system?

[daluu]

Sure would be nice if there was an easy way to track/confirm the latest/up-to-date email-to-SMS gateways for all these carriers. Do these carriers list/expose this info publicly somewhere? Or you have to snoop around online to find them out?

[typpo]

Any improvements recently? I think some providers temporarily blacklisted - I am getting texts just fine on Verizon.

I'm thinking of adding a global daily limit to prevent these sorts of outages.

[ntpeters]

I just started playing around with textbelt, and currently can't receive texts on T-Mobile or my Google Voice number (not sure if Google Voice was ever supported though?)

[karlderdmann]

keep getting a 404 response, no luck sending to a google Voice or Verizon, using Postman.

[daluu]

FYI, Google Voice isn't supported, see #27

[typpo]

@karlderdmann Can you show us your code? The site and service are up and you shouldn't be getting a 404.

[WindfallLabs]

Just tested this with a friend's Version phone (worked fine) and my piece of junk Sprint phone (message never arrived). Could anyone double check Sprint support?

[SnowySailor]

Testing on a locally-run node server with Verizon and I am getting success : true with my reply, but I am getting no texts sent to my phone. Very confusing.

[FelipeCarnevali]

In Brazil doesnt work. In the Australia too. My company of cell phone in brazil is the Claro. When i sended the message, return true but the message dont arrived.

[trevalexandro]

I know I'm late, but I'm trying to hook into the API and my Verizon phone is getting no messages even though I'm getting a 200 HTTP response.

[typpo]

@trevalexandro I assume you are self-hosting. Can you provide details of your setup? Outputs on the server and client?

[sidpagariya]

@daluu Google Voice seems to work through the official API from textbelt.com/text but not from my standalone server...could you verify that, @daluu, @typpo, or @ntpeters?

Thanks!

[daluu]

I believe the public API no longer uses the same underlying mechanism as the standalone server since you have to pay for it (so it works better with more reliability), the standalone server is what was originally the public service as well, and that mechanism I believe never worked for Google Voice.