RobSpectre

10 ms·

91.
by RobSpectre 13y ago
Always appreciate your support Josh. much work to do before this incident is resolved fully.
92.
by RobSpectre 13y ago
It has been some time since we have had an incident this disruptive for our customers. Looking forward to delivering that investigation summary to you as soon as we feel we got it right.
93.
by RobSpectre 13y ago
Thank you very much for that - our work is still not done. Through the night we have identified what we believe to be the root cause and have reconstructed the timeline that produced the incident. We still owe you a full technical post mor
94.
by RobSpectre 13y ago
Good to know. Very sorry again.
95.
by RobSpectre 13y ago
Rob from Twilio again. Our CEO Jeffiel just posted an update on the situation on our blog which can be found here: http://www.twilio.com/blog/2013/07/billing-incident-update.h... Full text also here: At 3:28
96.
by RobSpectre 13y ago
We are working cautiously on restoring full billing service to all accounts. We are trying to err on minimizing further billing impact to our customers as we restore service and, as such, taking each step carefully. This will also affect t
97.
by RobSpectre 13y ago
Lot of work still to do to make this right, but thank you very much.
98.
by RobSpectre 13y ago
Very sorry for this mistake. 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?
99.
by RobSpectre 13y ago
Very sorry for the inconvenience here and appreciate you opening a ticket for it. More to come.
100.
by RobSpectre 13y ago
Thank you very much for the support. Lot of work to do to make up for this shortcoming.
101.
by RobSpectre 13y ago
Thank you very much for that shakes. Grateful we have you in our community. We fell short of your expectations today. More later today on how we'll get this right.
102.
by RobSpectre 13y ago
Thank you very much for that. We came up way short for you this morning - committed to making it right.
103.
by RobSpectre 13y ago
Response is not good until everyone affected has their money returned to them and we explain what happened. Very much appreciate your support through a difficult night and morning. More to come.
104.
by RobSpectre 13y ago
Absolutely unacceptable. As I indicated above Daniel, if you haven't shot a note to help@twilio.com indicating you're affected by the incident, please do so we can communicate directly when this $480 mistake is corrected.
105.
by RobSpectre 13y ago
Definitely not nice for anybody. We will make this right.
106.
by RobSpectre 13y ago
I'm very sorry to hear that, but understand your frustration. As I indicated above, please shoot us a note to help@twilio.com so we can make this right for you.
107.
by RobSpectre 13y ago
I agree - this is not our best work. We'll have more on what caused this incident and what we're going to do to make it right later today. OP link directs to the board with our up-to-the-minute status on resolving this incident.
108.
by RobSpectre 13y ago
The account balance in your Dashboard UI will have some changes as we continue our recovery work. If you haven't already, please send an email to help@twilio.com so we can let you know directly the resolution for this billing error.
109.
by RobSpectre 13y ago
I think that reaction is entirely appropriate in this case. We just unsuspended the accounts affected by this incident and are currently working on the balances. If you haven't already, please send an email to help@twilio.com indicatin
110.
by RobSpectre 13y ago
We are actively working on the incident and have identified the accounts affected. There will be account balance changes in the Dashboard UI as we address the erroneous billing. If you haven't already, please send us an email to help@t
111.
by RobSpectre 13y ago
Rob from Twilio here. We are still actively working on this incident and aware that erroneous auto-recharge billing and account suspensions have occurred for a number of customers. If this has happened to your account, please send an email
112.
by RobSpectre 13y ago
Thanks partner. Lot of work before we get there - looking forward to the next leg of the mountain.
113.
by RobSpectre 13y ago
Thanks so much gales. You are right - there is a whole lot of work ahead.
114.
by RobSpectre 13y ago
Thank you . Hope to see you there - we've got some serious fun planned.
115.
by RobSpectre 13y ago
Thank you very much for that. Still much work ahead - glad you are with us for it.
116.
by RobSpectre 13y ago
Randall - this is awesome! Congratulations on your launch.
117.
by RobSpectre 13y ago
While I can empathize with Olemis on the reception of Brython on Hacker News, I'm not sure one can infer from that exchange (or the admittedly high number of similar conversations) that developers are incapable of being impressed. This just
118.
by RobSpectre 13y ago
@djinteractive was actually kind enough to submit a pull request with a calmer red. Looks much improved.
119.
by RobSpectre 13y ago
Yeah. My bad. :/
120.
by RobSpectre 13y ago
Lot of disinformation spreading about this. All I know is my friends couldn't call their folks, so I wrote the app. No idea what the diagnosis or prognosis on the situation is there - we'll keep it up until we hear all the telecom infrastr

More ›