For Twilio accounts, there is an option to add a TOTP secret, and use it when logging in. But, they don't support disabling the default SMS method, and using TOTP exclusively. When you authenticate using TOTP, you still have a fallback option to receive a SMS code.
So, in the case of Twilio, the TOTP feature only improves convenience, not security. At least that was the case when I looked a couple months back. I opened a support ticket about this, and they acknowledged the problem, and that was it.
We recently wrote an article comparing the infrastructure setup of various communication API platforms and how that affects their reliability. We'll have to see if Twilio says this was from their network or some other internal problem. https://voximplant.com/blog/where-cpaas-deploy-their-network...
One thing that I find interesting about that, is that's -just- after the TCPA window opens in the EST time zone. The other reason that raises my brow is this status update...
> Twilio services are now operating normally, however processing of Programmable Messaging queues was delayed during the incident.
9 comments
[ 3.1 ms ] story [ 97.3 ms ] threadFor Twilio accounts, there is an option to add a TOTP secret, and use it when logging in. But, they don't support disabling the default SMS method, and using TOTP exclusively. When you authenticate using TOTP, you still have a fallback option to receive a SMS code.
So, in the case of Twilio, the TOTP feature only improves convenience, not security. At least that was the case when I looked a couple months back. I opened a support ticket about this, and they acknowledged the problem, and that was it.
One thing that I find interesting about that, is that's -just- after the TCPA window opens in the EST time zone. The other reason that raises my brow is this status update...
> Twilio services are now operating normally, however processing of Programmable Messaging queues was delayed during the incident.
Emphasis mine.