Thailand Locks Out Bitget on December 5, and the Bill Just Came Due for Unlicensed Exchanges
Thailand's regulator is cutting Bitget off at the knees on December 5, and users are being told to sort out their holdings before the door closes. Bitget says guidance on service access is coming. What it won't say is why this was always going to happen.
Thailand just handed Bitget a deadline, and this one has teeth. December 5 is the cutoff. After that, Thai customers should plan on being locked out.
That's the whole story, and it's bigger than one exchange.
The regulator wants users to deal with their holdings before the block lands. Bitget says it'll push out guidance on what service access looks like on the other side. No extension announced. No rescue deal. No soft landing. And just like that, one of the loudest offshore exchanges on the planet gets escorted off a market of roughly 70 million people.
So who's actually surprised? Nobody who's been paying attention.
The Deadline Is Real
Thailand has run a licensing regime for digital assets since the 2018 emergency decree. If you want to serve Thai customers with a real operating footprint, you get a license from the Securities and Exchange Commission. Bitkub did. Gulf Binance did, launching in-country in January 2024. Upbit Thailand and Bitazza did too. The list is short, it's been short for years, and everyone knows their names.
Bitget isn't on it.
That's the part the offshore crowd keeps pretending doesn't matter. It does. It always did. Thailand's SEC has been steadily walking toward a hard-access model, where the regulator doesn't just warn and fine, it pulls the plug. December 5 is that model in action.
And the sequencing is smart. Warn first, then force users to move their own money on their own time, then cut access. Customers can't claim they got sandbagged. They got a date.
But here's the number that should worry every exchange exec reading this. Bitget claims more than 45 million registered users globally. Thailand is nowhere near the top of that book. Which means Bitget can afford to lose it, and the Thai regulator can afford to enforce it. Two parties with minimal use on each other. That's how deadlines actually stick.
This changes things for every unlicensed platform in every market with a serious regulator. If Thailand can do it with one press release and a calendar date, so can Brazil. So can Indonesia. So can South Korea, which has already been running a version of this playbook.
Traders are watching closely. The ones with funds stuck on the wrong side of the line are watching hardest.
Who Wins, Who Loses
The winners are obvious and they're about to get paid for patience. Licensed Thai operators get a forced migration of users, wallets, and trading volume handed to them by a regulator. Bitkub is the big fish. Gulf Binance is the hungry one. Both just got a free marketing budget courtesy of the SEC.
The losers are Bitget's Thai user base, who now own a logistical headache with a hard deadline attached. And arguably Bitget itself, which loses a real chunk of Southeast Asian volume at a moment when competition in the region is brutal.
But the biggest loser is the version of crypto that assumed borders were a suggestion. That era is closing. Quietly, market by market, deadline by deadline.
My hot take: this block won't stop one determined Thai trader from accessing Bitget. It'll just push them onto a VPN, offshore rails, or a peer-to-peer desk with worse pricing and zero recourse if things go sideways. Regulation by blocking access doesn't eliminate the activity. It downgrades the safety of it. That's a genuine cost, and the people paying it are retail users with $400 in altcoins, not anyone with real size.
Second hot take: the exchanges that spent years and real money on licensing are about to look like geniuses. The ones that called licensing a tax on growth are about to spend December explaining to their own support teams why their users can't withdraw.
The Counterpoint
Steelman the other side for a second, because it's not weak.
Thailand's licensing framework is restrictive. It limits what domestic platforms can offer, it keeps token listings thin, and it leaves Thai users with fewer products than a global exchange would hand them. Bitget offers derivatives, deep liquidity, and a catalog that a licensed Thai venue simply can't match. If you're a trader in Bangkok who wants use on a mid-cap, the licensed option may not exist at all.
Which is exactly why the demand is there. And why the block could backfire by pushing volume into the shadows rather than into Bitkub's order books.
There's also the softer read. Bitget isn't being accused of fraud. It's being told to get a license or get out. A company with 45 million users has the balance sheet to do that if it wants the market badly enough. So maybe December 5 isn't a door slamming. Maybe it's a negotiating position. Get licensed, come back, keep the users.
That's the bull case. It's real. It's just not likely on a 30-day clock.
The Verdict
Here's the call. Thailand is right, and Bitget will probably comply eventually, and the users in between get squeezed.
Regulators need a way to reach bad actors before the damage lands, and a license is the only mechanism that's ever worked. Everything else is a strongly worded letter. Thailand has decided letters aren't enough. I can't argue with the logic, even when I don't love the outcome.
What I'd argue with is the execution gap. A deadline without a mandatory, cheap, safe migration path just creates a 10-day scramble and a wave of support tickets. December 5 arrives, and a slice of users will still have funds sitting there because they didn't read the email. Those people don't get made whole. They get a lesson.
So if you're a Thai Bitget user, move your assets now. Not December 4. Not the night of. Now.
The market's verdict on this one is simple. Licensing stopped being optional in most serious jurisdictions roughly two years ago. Thailand just made that official with a date on it, and none of the offshore exchanges should be shocked that a sovereign government prefers its own rulebook to someone else's terms of service.
December 5 is coming. The clock's already running.