BitFlyer Flags XLM Deposit Disruption Linked to Stellar API Restrictions

Incoming Stellar Lumens (XLM) transfers stopped landing normally in customer accounts at bitFlyer. The Japanese exchange identified the start time as approximately 11:49 p.m. Japan Standard Time on October 19, 2026, and attributed the problem to restricted access to the Stellar API used for bitFlyer XLM deposits.

The disruption impacted incoming crediting exclusively. In the same notification, bitFlyer confirmed that customers could still send XLM, while transfers of all other supported cryptographic assets continued operating normally.

BitFlyer XLM Deposit Transfers Were Not Appearing Normally in Accounts

The impacted transactions involved XLM sent to bitFlyer from external platforms. Sending Stellar Lumens to the exchange during this window meant deposits could experience delays before reflecting in customer balances.

The status advisory traced the issue back to late Monday, October 19. The malfunction specifically affected the exchange’s processing of inbound payments, meaning receipts were not credited “as usual,” according to bitFlyer.

2026 年 10 月 19 日（月）午後 11 時 49 分頃から、XLM の公式 API（ Stellar Development Foundation ）へのアクセス制限の影響により、ステラルーメン（ XLM ）の受取が正常に反映されない事象が発生しております。

現在、代替手段による受取反映の再開に向けた対応を進めております。…

— bitFlyer status (@bitFlyer_status) October 20, 2026

BitFlyer Links the XLM Disruption to API Access Restrictions

Inbound XLM transactions operate through the official Stellar Development Foundation API. BitFlyer noted that access restrictions on that specific service interrupted its standard crediting procedure.

“This is due to access restrictions on the official Stellar API (Stellar Development Foundation), which bitFlyer uses,” the exchange stated.

The root of the issue lies within the pathway bitFlyer utilizes to display incoming XLM within user accounts. The platform announced it was developing alternative methods to credit those receipts, making restoration of that pipeline the immediate priority.

XLM Withdrawals and Other Asset Transfers Remained Available

BitFlyer maintained a clear distinction between incoming XLM crediting and its broader transfer capabilities. Sending Stellar Lumens remained fully operational under the terms of the notice, alongside the depositing and withdrawing of every other supported digital asset.

While functional withdrawal options offered little consolation to users experiencing Stellar deposit delays, the exchange kept those separate functions open while workaround procedures focused solely on inbound receipts.

BitFlyer’s Resumption Announcement Is the Next Milestone

At the time of U.Today’s October 20 report regarding the incident, bitFlyer was actively striving to restore crediting via alternative solutions. The exchange issued an apology for the inconvenience and committed to releasing a follow-up announcement once normal inbound XLM crediting is re-established.

“We will provide a further update once the crediting of incoming XLM transfers has resumed,” bitFlyer stated.

That upcoming resumption notice serves as the primary benchmark. For the service interruption detailed in the October 19 advisory, success will be measured by whether incoming XLM successfully populates bitFlyer accounts as normal, independent of the status of unaffected withdrawal services.

FAQ

When did bitFlyer’s XLM crediting disruption begin?

BitFlyer estimated the start time at roughly 11:49 p.m. JST on Monday, October 19, 2026, as specified in its official service advisory.

Which incoming XLM transfers are affected by the notice?

The notice pertains to Stellar Lumens transferred from external origins into bitFlyer accounts, specifically impacting the routine crediting process required to reflect those receipts in user balances.

Can customers still send XLM from bitFlyer?

Yes. BitFlyer explicitly exempted sending Stellar Lumens from the listed service disruptions in its October 19 announcement.

Are deposits and withdrawals of other supported crypto assets affected?

No. BitFlyer confirmed that sending and receiving all other supported crypto assets remained fully operational, as the issue was isolated to incoming XLM crediting.

What event did bitFlyer say would trigger its next update?

The exchange pledged to issue a subsequent update once inbound XLM crediting has successfully recovered through its deployment of alternative processing methods.

This article is for information only and is not financial advice.

Additional FAQs

Why were XLM deposits delayed on bitFlyer?

Deposits were delayed due to restricted access to the official Stellar API provided by the Stellar Development Foundation.

Did the issue affect XLM sent from external wallets?

Yes, the problem specifically targeted incoming XLM transfers sent to bitFlyer from external sources.