In this guide, we will show you the steps to fix the issue of Two Factor Authentication not working on Twitter. Out of all the social media platforms, Twitter was the one that silently carried out its task in the background without being much in the limelight. However, ever since Elon Musk decided to step in, this platform has been in the news every other day, and not for all the right reasons.
From reinstating questionable accounts to degrading the value of blue tick by making it available for everyone to purchase, and even firing employees at his whims and fancies, the entire platform is currently in a ruckus. Things aren’t going great in the backend either. As of now, they have decided to trim down the micro-servers from 1200 to just 40.
As expected, this is sure to have an adverse impact on the overall functioning of this service. And that has indeed been the case. Some of the micro-services were crucial for the proper working of Two-Step Verification. However, right after the reduction of servers, many users voiced their concern that the Two Factor Authentication is not working on their Twitter accounts.
They keep on waiting for an eternity for the code to arrive but never happens, even though Twitter displays them a false positive that ‘We sent you a code’. All in all, all the users who have 2FA enabled on their accounts are unable to log in to it. If you are also in the same boat, then this guide will make you aware of a nifty workaround to rectify this bug. Follow along.
Fix Two Factor Authentication not working on Twitter
As of now, only the SMS-based two-factor authentication is bugged, email and app-based 2FA are working well and good. So for the time being, you should select the latter two options when logging in to your account, You will then receive the code within a few seconds which you could use for sign-in purposes right away.
So these were the steps to fix the issue of Two Factor Authentication not working on Twitter. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned workaround is your best bet.
