Japanese retail broker GMO Gaika restored its trading systems on October 7 after a broad technology outage disrupted browser access and a long list of account, funding, withdrawal and authentication functions across its FX, CFD and options services.
The broker first acknowledged that it was checking problems with its trading system at around 05:10 JST. By a later update, GMO Gaika said customers could not log into its PC or smartphone browser-based trading tools and advised them to use the company’s Gaika ex mobile application or Gaika ex for Windows instead.
The disruption extended well beyond browser login. GMO Gaika listed quick deposits, bank-transfer deposits, withdrawal requests, withdrawal cancellations and deposit and withdrawal history among the affected functions. Customers also faced restrictions involving password changes, registered-account information, authentication-method settings for passkeys and SMS, passkey registration, password resets, login-ID inquiries and account unlocking.
Access from the FX platform into GMO Gaika’s options and CFD products was also affected, while customers could not apply for new CFD accounts through the impacted system.
At approximately 09:40 JST, GMO Gaika said recovery work had been completed and that all trading tools and functions were once again operating normally. Roughly four and a half hours therefore passed between the company’s first public notice and its recovery announcement.
GMO Has Not Said Whether Order Execution Was Directly Affected
The most important unanswered question is what happened to actual trading during the disruption.
GMO Gaika referred broadly to problems involving its trading system, login failures and function restrictions, but its public notice did not specifically say that FX or CFD order entry, execution, modification or cancellation had failed across the platform.
The company’s recommendation that customers use its mobile app or Windows application suggests that at least some trading access remained available while browser tools were unavailable. That is materially different from a complete trading-engine failure.
For comparison, a recent 65-minute order-processing incident at CMC Markets explicitly raised questions over whether customers could submit, change or cancel orders during live market conditions. GMO Gaika has so far provided less detail on whether its October 7 problem reached that part of the trading workflow.
The distinction matters for customers holding leveraged positions. Losing access to account settings or deposit functions is disruptive, but being unable to close or modify an FX or CFD position while markets are moving can create direct financial losses.
GMO Gaika has not publicly disclosed how many users were affected, whether any orders failed or were delayed, whether customer balances were incorrectly displayed, or whether any clients sought compensation after being unable to access positions.
The Outage Reached Funding, Withdrawals and Security Functions
What makes the incident notable is the number of customer journeys affected at the same time.
Quick deposits and ordinary bank-transfer deposits were unavailable through affected functions, while customers also could not submit or cancel withdrawal requests or view deposit and withdrawal histories. That means the incident touched both sides of the cash-management process rather than being limited to trading charts or a public website.
Account-security functions were also caught in the disruption. Users faced restrictions around password changes and resets, passkey registration, authentication-method settings and account unlocking.
This resembles a broader industry problem in which an institution can remain operational at the infrastructure level while a particular access route prevents customers from reaching their accounts. Dave Finances recently examined a login disruption at Crypto.com that left its wider exchange functioning but temporarily blocked some Android users from accessing it through their normal application.
Alternative access is valuable, but only if customers know that it exists and can successfully authenticate through it when the main channel fails.
GMO Gaika Had Another Browser Login Incident in June
The October outage was not the broker’s first access-related technology problem this year.
On June 1, GMO Gaika reported browser login difficulties affecting Gaika ex, its Optore binary-options service and Gaika ex CFD. That incident ran from around 08:00 until 13:30 JST, or approximately five and a half hours, and customers were again directed toward alternative trading tools.
The June incident was narrower. GMO described difficulty reaching and logging into browser trading screens, whereas the October event extended across deposits, withdrawals, account information, security settings and cross-product access.
There is no public evidence that the two outages shared a technical cause, and it would be premature to describe October’s problem as a recurrence of the June defect. Still, repeated access incidents become more relevant when evaluating operational resilience because customers care about both the duration and frequency of failures.
GMO Gaika was founded in 2003 and became part of GMO Financial Holdings in 2021 before adopting its current name in 2023. Its historical disclosures show that the broker had already passed 400,000 total accounts by 2020, giving technology incidents potential significance across a sizeable retail user base.
The company operates FX, CFDs and binary options and is registered as a financial instruments business operator in Japan. GMO Gaika appears under Kanto Local Finance Bureau registration No. 271 on the Financial Services Agency’s register of licensed financial instruments firms.
For Traders, an Outage Is Really About Which Layer Failed
Calling something a “system outage” can hide enormous differences in actual financial risk.
If a marketing website fails, the economic consequence is usually small. If login authentication fails but a second application still works, customers face inconvenience but retain a possible escape route. If order routing, pricing or execution stops, the outage becomes a different category entirely.
That was the lesson from the recent trading infrastructure outage at Polymarket, where parts of the market-facing interface remained available even while underlying APIs, market data and settlement infrastructure were degraded.
For GMO Gaika, investors and customers therefore need more technical detail before judging the severity of October 7 solely by its four-and-a-half-hour public timeline.
If traders could still open, close and manage positions normally through the mobile and Windows applications, the event looks primarily like a broad access and account-management outage. If the underlying execution layer was also impaired, the risk profile becomes much more serious.
Alternative Trading Channels Reduce Risk, but They Do Not Eliminate It
GMO Gaika’s decision to direct customers to separate applications highlights one of the most important defenses against financial-platform outages: redundancy.
A web interface, desktop application and mobile application can give traders multiple routes into the same account. But those routes are only truly independent if they do not all rely on the same failed authentication service, backend database or order-management component.
The difference becomes especially important for leveraged products. During a planned full trading blackout during Kraken’s NinjaTrader maintenance, customers were explicitly warned that market risk could continue even while they temporarily lost the ability to manage orders. Unexpected outages create a harder problem because traders receive no opportunity to reduce exposure beforehand.
That is why the most useful follow-up from GMO would be a root-cause explanation that identifies which systems failed, whether alternative applications were fully functional throughout the incident and whether any orders, deposits or withdrawals remained delayed after the platform was declared restored.
The Next Question Is Whether GMO Publishes a Root Cause
For investors, one isolated outage rarely changes the economics of a brokerage business. Technology problems happen even at large, heavily regulated financial institutions.
What matters is whether problems begin to form a pattern and how transparently management responds when they do.
GMO Gaika’s June browser incident and October’s broader disruption do not yet prove a systemic reliability problem. They do, however, make operational resilience worth watching more closely, especially because the latest outage touched trading access, cash movement and security functions simultaneously.
A detailed post-incident report would help distinguish a contained software or infrastructure failure from something that exposed deeper dependencies across GMO Gaika’s systems.
For customers, the practical questions are simpler: could every open position still be managed, did every deposit and withdrawal eventually process correctly, and did anyone incur a loss specifically because the platform or an access channel was unavailable?
Until GMO answers those questions or customers produce order-level evidence showing otherwise, the confirmed conclusion remains narrower. The broker experienced a broad multi-product system outage on October 7, restored all reported functions by around 09:40 JST and left the most financially important detail — whether actual trade execution was impaired — publicly unresolved.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape.