Well, since they don't provide an SLA you can't really hold them accountable. Does that mean you shouldn't build services for which you charge money on top of twilio?
Is twilio better suited to internal use rather than for building SaaS apps?
These are serious matters.
Re:How Twilio screwed us over
by wccrawford on Saturday September 25, 2010 @07:03AM
(#1726734)
If you give an SLA for your service, you had better have SLA all the way back down the chain. So yeah, it does mean that you shouldn't charge money for services built on Twilio (until they have an SLA) if you intend to provide reliable service yourself.
> The email from twilio informed me they had, without warning switched off all international SMS functionality. ...they were able to massively degrade the functionality of our app – an app which not only do people pay for, they rely on.
Which I suppose is interesting enough, but then:
> But when it comes what really matters, being able to offer my customers a reliable service, you need a written agreement.
Which isn't exactly profound wisdom. If you're charging people for a service, you better make sure that you can hold your backend providers accountable for their end of the chain.