More from this creator
Other episodes by Kitty Cat.
More like this
If you liked this, try these.
Transcript
The full episode, in writing.
Picture this: you open your phone, tap the familiar blue bird, and instead of your timeline, you get a message—account locked. It wasn’t just you. It was millions. The Great Twitter Lockout of 2023 hit hard and fast, and if you weren't ready, you lost access—possibly for good.
So what really happened? In November 2023, the company now officially rebranded as X announced it would retire the Twitter.com domain and lock accounts that hadn’t updated to the new system. This wasn’t just a name change. Overnight, access through Twitter.com was revoked, and only those who had migrated their accounts to the new X platform and agreed to new terms could get in.
Why did it go down like this? The company was pushing a massive, high-velocity rebrand. By November 10, 2023, they planned to redirect all Twitter.com traffic directly to X.com. That meant the end of the Twitter brand as people knew it—no more blue bird, no more tweets, and, crucially, no more access to old accounts if you didn’t act in time.
The background here is a year of sweeping changes. After the rebrand to X, the company started phasing out Twitter branding in stages. First, there were interface tweaks—logos swapped, terminology updated, and the iconic bird icon replaced with a stark X. But the real drama started when users realized the changes were more than cosmetic. By late October 2023, X began sending out warnings: update your account, agree to new terms, or you’ll lose access when Twitter.com goes offline.
And then came the lockout. At 12:01 AM on November 10, 2023, hundreds of thousands of users who still used Twitter logins or hadn’t re-registered on X found their accounts inaccessible. For users who built entire communities, businesses, or personal brands on Twitter, losing access meant more than inconvenience—it meant critical data, contacts, and posts potentially gone forever.
Why the hard cutoff? The company cited “security and brand consolidation.” They wanted to eliminate confusion, streamline user data, and—according to official statements—prevent phishing and account hijacking risks that could come from maintaining two parallel login systems. But for users, the effect was jarring. Some had relied on Twitter logins for years, using the same credentials since the early 2010s. Others, including journalists and activists, suddenly found themselves locked out of DMs, archives, and even two-factor authentication methods that depended on email addresses they no longer had access to.
The lockout didn’t just hit casual users. Several high-profile media organizations had corporate accounts tied to Twitter.com that were locked because IT departments didn’t migrate in time. In one well-documented case, a newsroom with over 1.2 million followers lost access to its account for 48 hours until it complied with the new X registration.
Technical glitches compounded the chaos. Some users who attempted to migrate during peak hours encountered error messages, failed login loops, or incomplete data transfers. According to support reports cited in November, help desk tickets tripled in volume in the first week after the lockout, with wait times exceeding 72 hours in some cases.
One immediate consequence was the surge of imposter accounts. Within days, dozens of “legacy” Twitter accounts were cloned by users on X, sometimes using nearly identical handles and profile images. The confusion sparked warnings from digital security experts, who noted that verification on X was not retroactively applied to all old Twitter accounts, leaving the door open for scams.
The scale was enormous. Estimates from industry analysts at the time suggested that around 17 million inactive or slow-to-migrate Twitter users lost account access during the lockout window. That’s roughly equivalent to the population of the Netherlands. For perspective, Twitter’s active user base before the lockout was estimated to be around 240 million worldwide.
Not everyone was caught off guard. Some power users had been tracking the domain retirement for weeks, sharing migration guides and archiving tools to help communities save old threads, media, and data. The Internet Archive reported a spike in requests to save Twitter.com profiles in the 36 hours before the cutoff.
But for others, the moment of discovery was abrupt. Some tried to log in after weeks away and found their account “permanently locked.” The only appeal option was to start the account recovery process on X, which—according to the company’s own FAQs—could not guarantee the restoration of data or followers.
Twitter wasn’t just a site—it was the home of movements, fandoms, careers, and news. Losing an account wasn’t just about losing memes or old posts; it meant losing years of professional contacts, DMs, and, in some cases, digital proof of work for journalists and historians.
The lockout also fractured online communities that once depended on Twitter’s open API. Some bot accounts, which had provided real-time alerts for weather, news, or public safety, suddenly went dark. The API, which had always been accessible at Twitter.com endpoints, now required new permissions and keys under X’s policies. Some open-source projects and hobbyist bots simply ceased to function.
Researchers relying on Twitter.com links saw swathes of references break overnight. The redirection to X.com sometimes resulted in 404 errors, making years of documentation and citation suddenly inaccessible.
The debate raged about whether the company had given enough notice. Official statements claimed users were notified by email, in-app alerts, and banners, but screenshots from users showed that some never received a warning. Some international users claimed that translation errors in the warning messages led them to dismiss the alerts as spam.
A particularly weird footnote: several artists and creators reported that their Twitter “verified” blue checkmarks did not automatically transfer to X.com accounts. This led to frantic attempts to reclaim verification, with some creators paying for new verification packages—sometimes with no immediate result.
What was the company’s explanation for the timing? One spokesperson said the November 10 date was chosen to coincide with the official launch of new X-branded web apps and to streamline the company’s infrastructure. By cutting over all global domains in a single sweep, the company aimed to avoid “fragmentation of user experience,” but this meant a single shock event rather than a slow phase-out.
Some privacy advocates raised alarms about data retention. Users who didn’t migrate had their data “archived” under X’s new terms, and, according to documentation, would need to submit a special request to retrieve their information—a process that could take up to three weeks.
There was also a legal angle. Under European Union data protection regulations, users had the right to request deletion or retrieval of their account data. Reports emerged that, in several EU countries, local data protection agencies received hundreds of formal complaints in the days after the lockout, mostly from users unable to recover years of private messages and media.
A detail that caught many by surprise: all tweets scheduled via Twitter.com’s native scheduler were deleted if the account wasn’t migrated by the cutoff. Several brands discovered that entire holiday marketing campaigns, scheduled months in advance, simply vanished.
The lockout marked the end of a digital era. The familiar Twitter.com login screen was replaced by a stark X-branded portal, with no option to access legacy content unless migration was completed. The company removed all references to “tweeting” from help pages and marketing materials. Even the term “tweet” was expunged from official documentation.
In the weeks after the lockout, alternative platforms like Mastodon and Bluesky saw a spike in signups. Some communities, especially fandoms and political organizers, coordinated mass migrations in signal groups and Discord channels, sharing lists of old handles and new usernames to stay connected.
Within a month, several prominent hashtags related to the lockout trended on X, including #GoodbyeBlueBird and #TwitterLockout2023. These trended even as X’s algorithm began prioritizing the new brand language and suppressing references to “Twitter.”
The technical migration was ambitious. Engineers had to redirect billions of legacy URLs, update OAuth integrations for third-party apps, and run background scripts to flag accounts not in compliance with new X terms. According to one leaked internal memo, the engineering team ran automated scripts over 48 hours to process the lockout, with error rates reportedly below 0.5%.
But glitches persisted. Some users, especially those with multiple linked accounts, reported being locked out of both personal and business profiles, requiring separate recovery for each one.
One developer quirk: some Twitter.com email notifications—such as password resets and DM alerts—continued to be delivered for up to 72 hours after the domain retirement, due to caching issues with third-party mail providers. This led to confusion, as users received notifications for accounts they could no longer access.
The lockout also redefined digital identity. For over a decade, “@username” at Twitter.com was the default persona for millions. The shift to X.com broke countless website embeds, digital business cards, and even printed QR codes. Event organizers had to scramble to update promotional materials with new handles, sometimes missing major conferences or launches.
In the aftermath, several open-source archivists launched rescue projects to scrape and preserve public Twitter.com timelines before the final redirect. According to the Internet Archive’s official logs, over 3.5 million Twitter.com pages were saved in the week leading up to November 10, 2023.
A handful of celebrity accounts that failed to migrate became instant collector’s items—squatters claimed the old handles on X, and some even attempted to sell access or redirect followers.
One final twist: as of November 2023, the Twitter.com domain itself was configured to respond only to automated legal requests and government inquiries, with all public access permanently disabled.