Live data from Hacker News

Twilio blocked our account and with it hundreds of our customers [resolved]

news.ycombinator.com

11–20 of 165 posts

Re: Twilio blocked our account and with it hundreds of our customers [resolved]

#12
You might want to just spend a day and switch to Plivo.

I use both Twilio and Plivo, and they're both fine for sms.

(Twilio is running amok because there was a recent court case that providers could be held liable for actions of their clients, so last month you would have received update ToS from several cloud providers in your email.)

Re: Twilio blocked our account and with it hundreds of our customers [resolved]

#16
post #11

Terrifying to rely on another team's support staff for your business to exist.

In this time and age I think it's inevitable. Think AWS instead of Twilio for example.

AWS provides a service that you can use as a commodity, and with appropriate backups, can easily recover from. DNS is the magic here.

Unfortunately (with the exception of SIP dialling, which is extremely niche) there is no DNS for telephony. If your provider cuts you off, you can’t transparently move away, and number porting is slow.

Re: Twilio blocked our account and with it hundreds of our customers [resolved]

#19
post #11

Earlier quoted context omitted.

In this time and age I think it's inevitable. Think AWS instead of Twilio for example.

AWS provides a service that you can use as a commodity, and with appropriate backups, can easily recover from. DNS is the magic here. Unfortunately (with the exception of SIP dialling, which is extremely niche) there is no DNS for telephony. If your provider cuts you off, you can’t transparently move away, and number porting is slow .

Do you really think the typical aws customer can easily recover from being banned?

Re: Twilio blocked our account and with it hundreds of our customers [resolved]

#20
post #19

Earlier quoted context omitted.

AWS provides a service that you can use as a commodity, and with appropriate backups, can easily recover from. DNS is the magic here. Unfortunately (with the exception of SIP dialling, which is extremely niche) there is no DNS for telephony. If your provider cuts you off, you can’t transparently move away, and number porting is slow .

Do you really think the typical aws customer can easily recover from being banned?

From what I've heard surrounding the Parler incident, AWS worked _with_ Parler staff to get their data off the platform. Sure, it's not a hot-swap to Azure or metal or whatever, but it was nice to see that they didn't hold Parler's data hostage or just plain delete it.

I'd assume the same courtesy would be extended to any customer, provided their ToS breaches aren't significantly worse (read: illegal) and it's not a billing-related suspension.

Post reply on HN