Looks like a lot of comments on the original article are asking why Cloudflare didn't go with Google Authenticator, and I have to admit I'm curious about that m

Looks like a lot of comments on the original article are asking why Cloudflare didn't go with Google Authenticator, and I have to admit I'm curious about that myself. Edit: Cloudflare left an answer in the comments of their blog about why they chose Authy, so I'm copy/pasting it here: "Thanks everyone for your comments, we appreciate the feedback. Some insight on why we chose Authy (more on this in a blog post to follow)... 1. Authy app will support google authenticator tokens within the next 2 weeks. 2. We chose Authy to solve many of the problems with Google Authenticator. Once you start using Authy you'll notice everything works seamlessly. Google Authenticator on the other hand has a few problems: - If you lose your phone, there is no way to revoke access to your token. - Google Authenticator depends on the time of the phone to be right for it to work correctly (same as Authy). But Authy will automatically sync this time for you in the background so you never have to worry, your tokens will always work. - If you change your phone, Google Authenticator requires you to go and reconfigure all of your accounts. With Authy all your accounts are synced, so when you upgrade and re-install Authy everything will be setup the way you expect it. - Authy uses 256 bit keys, while Google uses 128 bit keys. - Last year RSA was compromised and all their clients had to manually reset their keys. Google Authenticator has the same issue, if the keys were ever compromised everyone would have to manually reset the keys. Authy has a built-in reset mechanism that will automatically reset the keys for you if they are ever compromised."