BitFlyer Blames Stellar API Restriction for XLM Deposit Delays Since October 19

BitFlyer Delays XLM Deposits Since 23:49

BitFlyer has asked its customers to take no action at all, and that is the entire instruction: Stellar (XLM) deposits arriving on the network have been crediting late since 23:49 Japan time on Monday, October 19, 2026, while the exchange repairs the intake behind them. The exchange's official announcement confirms that transfers sent to BitFlyer from external sources, including self-custody addresses or a hardware wallet, have not been reflecting in account balances at the usual pace since that timestamp. A user can watch the on-chain transfer go out and still find the amount missing from the exchange balance for a stretch afterward. The gap sits between on-chain delivery and balance display, which is the stage the restriction touches. A deposit credit is the bookkeeping step where an exchange applies an incoming transfer to a customer balance, and BitFlyer routes that step through the official API infrastructure maintained by the Stellar Development Foundation, the nonprofit organization that supports the chain's development. A current access restriction on that API, the announcement states, has disrupted the normal crediting process, so payments reach the ledger without being applied to accounts on time. The exchange says it is working to restart the crediting operations through alternative methods. The notice stops there: BitFlyer published it on Tuesday, October 20, after deposits had lagged through most of a session, and the company has shared no calendar for when incoming Stellar (XLM) will fully return to normal.

Stellar Volume Hit $33.2 Billion in Q3

The disruption stops short of the network itself. Stellar transactions were not suspended across the board: the lag sits specifically in the crediting of XLM transfers into BitFlyer accounts, while the chain's blockchain nodes kept settling payments. Outbound activity is untouched as well. Users can keep sending XLM, and deposits and withdrawals for the other supported crypto assets on the platform show no disruption. The Stellar network's rails, in other words, are running; one Japanese venue's deposit rails are the choked part. That distinction matters for reconciliation: funds sent into the exchange during the window are recorded on the ledger, and the pending piece is the balance update, not the transfer itself. The delay also lands against a quarter of steep growth in the network's usage. Stellar's third-quarter 2026 report put total volume at $33.2 billion, up 71% from the second quarter and 62% from the same quarter last year, as banks, stablecoin issuers and fund managers moved the network into active use across web3 settlement flows. Stablecoin transfer volume rose 121% quarter over quarter to $25.1 billion. Tokenized real-world assets closed the quarter at $4.1 billion, a 36% quarterly gain and a 548% increase against the same period of 2025. Our desk has tracked the institutional build-out behind those numbers: the DTCC's $30 trillion tokenization service set to open with Stellar (XLM) in 2027, Chainlink Data Streams activated to carry $3.54 billion in tokenized assets, and a recorded stretch of 12 million transactions with fees near $0.00012. Volume of that size sharpens the operational question the delay raises: the deposit pipeline serving a Japanese trading venue leans on a single API layer, and a restriction on that layer pauses balance updates for everyone sending XLM in.

COINOTAG's read: this is an operational dependency story, not a chain failure, and the exchange's own announcement is the document that says so. BitFlyer names its API access as the broken link, leaves sends and every other asset running, and offers no restoration date, leaving the only confirmed effect a delayed balance display for transfers sent since 23:49 on October 19. Markets have little to price from that alone: with deposits, not orders, disrupted, no support and resistance shift on XLM tracks to the notice in our reading. For anyone whose Lumens landed inside the affected window, the unresolved part is timing: until BitFlyer publishes a credit-restoration date, the question of when pending balances post stays open.