Bitget Suspends USDC Withdrawals on Base With No Reopening Date

The cryptocurrency exchange said the suspension would begin on September 22 at 00:56 UTC+8 because of wallet maintenance. Bitget did not provide an estimated completion time, saying instead that the reopening date would be announced separately.

The notice applies specifically to withdrawals of USDC using Base. Bitget did not announce a platform-wide suspension of USDC withdrawals, meaning the restriction should not automatically be interpreted as affecting every network through which the stablecoin is supported.

That distinction matters because USDC is increasingly a multichain settlement asset. Circle currently supports native USDC across 38 blockchain networks, including Base, Ethereum, Arbitrum, Solana, Polygon PoS and Optimism. The expansion of USDC across multiple chains means exchange customers can often have several possible routes for moving the same dollar-denominated asset.

However, the usefulness of those alternatives depends on whether the receiving platform or wallet supports the same network. Users attempting to move USDC specifically into the Base ecosystem could therefore face more disruption than traders who simply want to withdraw the stablecoin through any available chain.

Base Shows No Sign of a Network-Wide Outage

There is currently no indication that Bitget’s suspension was triggered by a wider Base network failure.

Base’s official status dashboard showed all systems operational, including mainnet, block production, the public RPC API, deposits, withdrawals and the transaction pool. The network also reported no incidents for September 21.

That makes the situation different from cases where exchanges halt asset movements because the underlying blockchain itself has encountered a security or consensus problem. Dave Finances recently documented how exchange restrictions can coexist with an operational blockchain when problems instead involve individual assets, bridges or exchange infrastructure.

Bitget has not disclosed which component of its Base wallet infrastructure requires maintenance. The company has not said whether the problem involves its nodes, hot-wallet systems, transaction-signing infrastructure, blockchain indexing, liquidity management or another backend component.

Without that information, it would be premature to identify a specific technical cause.

This Is the Second USDC-Base Suspension in Days

The timing makes the latest interruption more notable than an isolated maintenance notice.

Bitget’s support center shows that the exchange suspended USDC withdrawals through Base on September 18 before announcing that withdrawals had resumed on September 19. The latest suspension therefore puts the same withdrawal route back into maintenance only a few days after service was restored.

Bitget has also issued maintenance notices affecting USDC withdrawals on other networks during September. It suspended USDC withdrawals over Solana on September 17 and Optimism on the same date, while another notice earlier in the month involved USDC on Sonic.

Those notices do not prove that the incidents share a common cause. Exchanges regularly perform blockchain-specific wallet maintenance, and each integration can have separate technical requirements.

But repeated interruptions become more relevant when users depend on an exchange as a gateway between internal account balances and public blockchain infrastructure. A customer can still see USDC inside an exchange account while temporarily losing the ability to move it through the network they intended to use.

That difference between a displayed balance and practical withdrawal access has also become important in more serious cases involving withdrawal restrictions at centralized exchanges. Bitget’s maintenance notice is not comparable to a prolonged compliance hold, but both illustrate why asset availability and asset mobility are separate questions.

No Evidence of Missing USDC or a Solvency Problem

There is currently no evidence that the Base suspension reflects missing customer assets, a USDC reserve problem or financial stress at Bitget.

That is an important boundary because withdrawal interruptions can easily attract speculation after previous exchange failures. A temporary network-specific maintenance pause is materially different from an exchange being unable to honor customer withdrawals across its platform.

Cases involving broader customer access to funds typically involve much stronger warning signs, such as prolonged restrictions, unanswered questions over reserves, restructuring processes or uncertainty over whether liabilities can be met.

None of those conditions has been established in Bitget’s Base notice.

Analysis: The Missing Deadline Matters More Than the Maintenance Itself

Wallet maintenance is normal. An open-ended maintenance window is where the story becomes worth watching.

If Bitget restores USDC-Base withdrawals quickly, this will probably amount to routine exchange infrastructure work. Crypto platforms maintain dozens or hundreds of blockchain integrations, and temporarily disabling one route can be the safer option when engineers are modifying wallet systems.

The problem is that Bitget has not told users whether this is expected to last an hour, a day or considerably longer.

That uncertainty matters because Base is not simply another obscure withdrawal network. It has become a major Ethereum layer-2 ecosystem, and native USDC is integrated directly into its trading, payments and decentralized-finance infrastructure.

For users moving capital between an exchange and on-chain applications, the network choice can be part of the transaction strategy rather than a cosmetic preference. Someone planning to deploy USDC into a Base protocol cannot necessarily substitute Ethereum or Solana without first creating another transfer or bridging step.

Multichain Stablecoins Create More Choice but More Infrastructure Dependencies

USDC being available across dozens of networks is usually presented as a strength, and it is. Users are less dependent on a single blockchain and can select networks based on cost, speed, liquidity and application availability.

But multichain support also gives centralized exchanges dozens of separate operational connections to maintain.

Each chain can require nodes, wallet software, deposit monitoring, withdrawal processing, liquidity management and security controls. The blockchain can be working perfectly while the exchange’s connection to it is unavailable. That resembles recent wallet infrastructure degradation where the underlying network remained functional but one access layer experienced problems.

This distinction is increasingly important as crypto becomes more infrastructure-heavy. Users interact with an asset through multiple layers: the stablecoin issuer, the blockchain, an exchange or wallet, RPC infrastructure and sometimes bridges or decentralized applications. Failure at one layer can make an asset temporarily unusable through a particular route without affecting the asset itself.

Duration Will Decide Whether the Suspension Becomes Significant

The next important variable is simply time.

A maintenance pause lasting a few hours is unlikely to have meaningful implications for Bitget or Base. A suspension stretching into several days would create a different story, particularly because the same USDC-Base route was already suspended and restored days earlier.

Users should also watch whether Bitget begins restricting additional USDC networks. Multiple independent maintenance events would not automatically indicate a larger problem, but a widening pattern would make the exchange’s wallet infrastructure more relevant to investigate.

The distinction between custody and access is particularly important on centralized platforms. Unlike custodial wallet services, where operators directly control transaction execution for customers, users withdrawing from an exchange ultimately depend on the exchange to approve and broadcast the outgoing transaction.

For now, the available evidence points to a narrow operational issue rather than a Base or USDC problem. Base remains operational, Circle continues to support native USDC on the network, and Bitget has described the suspension specifically as wallet maintenance.

The more interesting question is whether Bitget restores the route promptly. If it does, the episode will look like ordinary infrastructure maintenance. If the suspension remains open-ended or is followed by further interruptions, the repeated loss of access to the same settlement route will deserve closer scrutiny.