Unpopular opinion: SMS isn’t dead for OTPs. Single-route SMS is.
One slow carrier → codes land late → users blame your app.
A fallback route fixes most of it, and that’s what we work on every day at secondfactor.ai
What’s your backup when SMS fails?👇
18
Phone verification in Node.js:
✅ /send-otp
✅ /verify-otp
Expiry, lockouts, retries: our problem now
Devs, be honest: what’s the most painful OTP bug you’ve had to fix? 👇
1
15
Unpopular opinion: your OTP isn’t the problem. The wait for it is.
Delayed code → resend 3x → wrong code → user leaves.
Every second matters in auth, and that’s what we obsess over at @secondfactorai
What’s the longest you’ve waited for an OTP? 👇
Your OTP bill is probably bigger than it needs to be.
At $0.05/verification, 10k users = $500 before channel fees.
Then add resend spam, SMS pumping and codes sent to dead numbers.
8 ways to cut it:
secondfactor.ai/blog/reduce-…
1
29
Passkeys won.
So why will the world still send 1.5 trillion SMS codes next year?
Because on day one, your new user doesn’t have a passkey. They have a phone number.
We dug into the data on SMS OTP vs TOTP vs passkeys 👇
secondfactor.substack.com/p/…
20
Your OTP was “delivered.”
So why didn’t your user receive it?
From carrier filtering and routing issues to sender registration and unreachable handsets, OTP delivery has more failure points than most businesses realize.
Here’s why OTPs go missing👇
secondfactor.substack.com/p/…
1
25
