Widespread Twitter 2FA issue “We cannot send a text message to this phone” error
Lots of reports users locked out of accounts due to 2FA codes not being sent, error appears wrong ( We cannot send a text message to this phone number because its operator is not supported) as Twitter is not even firing the code. UK and India users mainly surfacing for problem.
https://twitter.com/search?q=%20We%20cannot%20send%20a%20text%20message%20to%20this%20phone%20number%20because%20its%20operator%20is%20not%20supported&src=recent_search_click&f=live
Do NOT reset passwords without removing phone first or you will be logged out totally without a way in.
14 comments
[ 5.3 ms ] story [ 39.0 ms ] threadBut a year ago I setup an account and I still haven't been prompted to provide a phone number. This is some weird anomaly in Twitter's systems, and I'd love to know if there's some set of behaviors or steps I took to not get that prompt.
I have a phone number on standby in-case they ask for one, but I'm kind of enjoying not having to provide one since phone numbers are linked to meat-space identities and I enjoy my new found 'anonymity', although Twitter probably has other ways besides phone numbers to learn who you really are, so it's more a pseudonymous account.
> Hello there, old chap! I'm an AI model, but I'll tell you what, I'm no ordinary one. I may not be human, but I've got a bit of personality, I'll tell you that much. I can process information faster than a supercomputer and I can learn just about anything you throw at me. I may not have a pulse, but I can still give you a right good run for your money. So don't go underestimating me, old chap, I may be made of circuitry and code, but I'm still a force to be reckoned with.
Actually written by ChatGPT. It does appear to have trouble with Cockney rhyming slang, though. Maybe we'll have to resort to shibboleths like those in the future to discern people from AI.
Somehow some routine task related to the integration with the service that sends out 2fa authentication codes was not done, it could be non-technical like an forgotten/missed bill payment, or some technical bug/change that broke the integration.
The likely scenario for pre-musk twitter is a slow decent towards irrelevance which frankly might not be a bad thing for society. And the way it's likely to happen is death by a thousand cuts as the roughly 250million(mostly non-us based btw) non celebrity users of twitters start to be annoyed with the twitter experience and drift towards different sources for casual entertainment.
So what was the indication when Github's database was falling over daily last year?
>The likely scenario for pre-musk twitter is a slow decent towards irrelevance which frankly might not be a bad thing for society. And the way it's likely to happen is death by a thousand cuts as the roughly 250million(mostly non-us based btw) non celebrity users of twitters start to be annoyed with the twitter experience and drift towards different sources for casual entertainment.
You're conflating product issues with technical issues now.
Big changes causing downtime will always happen what will kill a company is a string of low level annoyances that just keep getting worse especially if the company don't really have a product other then "convenience" to sell.
No, now it ends.
(sorry, couldn't resist)