Twilio

21 engineers on Hacker News describe using Twilio first-hand: 6 endorse it, 2 regret it, 3 are mixed.

63%trust
21first-hand users
18in production
endorse 6mixed 3regret 2uses, no opinion

“grandstream phones that receive calls on twilio [because it's the only one that will ring up to 10 extensions on a single login]”

endorse · production · amyames · 2024-12-09 · source ↗ · wrong label?

“they blocked some (in our case) legitimate messaging traffic. We switched most of our traffic to another provider and are pleased.”

regret · production · 13 yr · djyaz1200 · 2022-01-06 · source ↗ · wrong label?

“We had issues where they also were shutting us off and were unresponsive for days at a time.”

regret · production · tonightstoast · 2022-01-06 · source ↗ · wrong label?

“We use Twilio and OpenVBX for our phone solution. It works good plus let's us automate a bunch of things”

endorse · production · davismwfl · 2014-11-14 · source ↗ · wrong label?

“They've even modified their privacy policy to make it possible for my team at EFF to use Twilio on campaigns we run.”

endorse · production · sinak · 2014-09-19 · source ↗ · wrong label?

“imo if you try to push sms faster that they can send it they should either queue the messages (as twilio does)”

endorse · production · pardner · 2011-12-19 · source ↗ · wrong label?

“Our favorite products are probably Outright (dead simple), Twilio (enables tons of phone system magic)”

endorse · production · edash · 2011-11-11 · source ↗ · wrong label?

“I do like that they don't charge dev rates, but it does cost 3x as much in production. And twilio works great with ruby”

mixed · production · dickeytk · 2011-09-20 · source ↗ · wrong label?

“I love Twilio, have used it in production apps, and will continue to use it in production apps.”

mixed · production · ccollins · 2011-06-10 · source ↗ · wrong label?

“We use Twilio, and I hadn't heard of Tropo. FWIW we're not totally over the moon with Twilio”

mixed · production · ra · 2010-12-12 · source ↗ · wrong label?

“I haven't used them in production, but I've started playing around with their voice API and it's pretty neat.”

endorse · personal · ze_dude · 2010-10-15 · source ↗ · wrong label?

“We send many thousands of delivery notifications per day on SMS over Twilio.”

neutral · production · jackconsidine · 2025-11-19 · source ↗ · wrong label?

“We are not directly a tmobile customer. We use Twilio.”

neutral · production · grumple · 2023-12-25 · source ↗ · wrong label?

“We also iterated heavily on the experience of recording yourself - e.g. tweaking our timeouts, moving from Twilio transcriptions to Whisper”

neutral · personal · eieio · 2023-12-23 · source ↗ · wrong label?

“I've been using Twilio for 3 years and this is the first time I've ever had an SMS rejected. I don't get it.”

neutral · production · 3 yr · another_comment · 2021-12-29 · source ↗ · wrong label?

“We wrote these library wrappers around third party services because they did not exist in a stable form: twilio wrapper”

neutral · production · jayrulez · 2017-01-31 · source ↗ · wrong label?

“Long story short is we switched to Twilio as a result.”

neutral · production · kaypro · 2015-07-24 · source ↗ · wrong label?

“some phone/sms cost from Twilio ($5-10)”

neutral · personal · hectormalot · 2014-03-22 · source ↗ · wrong label?

“Twilio logs told us that we were taking over 15 seconds to respond to many of their callbacks.”

neutral · production · michaelrkn · 2013-02-13 · source ↗ · wrong label?

“Twilio for SMS notifications ($0.01/message is bearable, and means there's room for a small profit)”

neutral · production · geerlingguy · 2012-12-10 · source ↗ · wrong label?

“We use twilio(first), then bulksms then clickatell and finally nexmo.”

neutral · production · danielpal · 2012-11-28 · source ↗ · wrong label?