81–90 of 123 posts
I'm glad they (and most of us) are not in the business of making insulin pumps or other software where such bugs could have potentially lethal consequences.
You mean you don't want to see a medical supply startup that "moves fast and breaks stuff"? I'm surprised we haven't yet...
Apologies for nit-picking at punctuation, but occasionally it matters :-) "Twilio is over-billing ..." = Twilio is charging more than they should. "Twillio is over billing ..." = Twilio has given up on billing. It's so over. Just my personal bugbear - but sometimes it's worth getting this sort of thing correct. Apologies if this is just a US/UK difference, also (I'm in the UK).
Not a single person was confused by this, including me, a British dude sitting in the middle of London.
I've been using Twilio for over 3 years now and haven't experienced any significant downtime or service issues. Their support has always been amazing. Obviously this situation sucks but if there's any company I'd trust to make it right it's Twilio. From a developer point of view, we all have bugs. I remember the first time one of my bugs impacted customers and it was awful. If there's any community that should be und…
We fell short of your expectations today. More later today on how we'll get this right.
I see a lot negative comments here. Frankly, I understand people's frustration, but I think Twilio are dealing with this in the right way. I was one of the customers affected. Luckily for me, my credit card automatically blocked the transaction after the 10th time I was auto-recharged, meaning I had a cap on how much I paid. I can totally understand the frustration of people discovering that they suddenly have 100's…
Lot of work to do to make up for this shortcoming.
My account was impacted by this as well, however, it looks like my credit card company blocked the fifth recurring bill (and I woke up to a call from the Fraud Team at my credit card), so no real damage has been done. Support answered my email within 10 minutes, and promised to help me clean everything up.
More to come.
Hit -- but we only see an overcharge (3x). Service seems to be back up. Do you have a support number our ops team can contact (they're paranoid).
Can you have your ops team reach out via help@twilio.com and we'll get them connected with a resource to keep them informed?
Apologies for nit-picking at punctuation, but occasionally it matters :-) "Twilio is over-billing ..." = Twilio is charging more than they should. "Twillio is over billing ..." = Twilio has given up on billing. It's so over. Just my personal bugbear - but sometimes it's worth getting this sort of thing correct. Apologies if this is just a US/UK difference, also (I'm in the UK).
Earlier quoted context omitted.
Thank you very much for that. We came up way short for you this morning - committed to making it right.
Seconding Willie's comments. I'm not your customer today, but seeing how y'all are handling this would make me feel confident to use Twilio should the need arise. When you get some time (I'm sure you have none right now), read some of the Dreamhost discussion below. You folks appear to be doing an excellent job responding to this.