A Blue Ocean ATS outage disrupted overnight U.S. stock trading across Bitget and Alpaca on October 21, while Binance separately changed the funding calculation for its U.S. equity perpetual futures after reporting connectivity problems at an unnamed major overnight alternative trading system during exactly the same period.
The disruption began at approximately 03:46 UTC, or 11:46 p.m. Eastern Time on October 20, when Blue Ocean ATS halted trading after intermittent connectivity problems involving an external network provider.
Trading resumed at approximately 06:30 UTC, according to incident information circulated by Blue Ocean and subsequent platform updates. Alpaca restored its overnight market data and re-enabled fractional-share trading shortly afterward, at 06:43 UTC.
What makes the incident particularly important is that the same underlying overnight-market disruption produced very different consequences depending on how each platform used U.S. equity infrastructure. Bitget lost overnight execution for several products. Alpaca lost the market data required to support fractional trading but continued routing whole-share orders elsewhere. Binance did not announce a trading halt at all, but instead removed affected pricing data from a funding-rate calculation for equity-linked perpetual futures.
Bitget Suspended U.S. Stock and rToken Overnight Trading
Bitget explicitly identified Blue Ocean ATS as the upstream system supporting its overnight U.S. stock operation.
The exchange said it temporarily suspended overnight trading for U.S. stock spot products, U.S. stock rTokens and related instruments while Blue Ocean’s overnight system was unavailable. Premarket and regular-session trading remained available.
Bitget also said customer assets and underlying funds were unaffected, but unfilled overnight orders could be frozen or canceled according to the applicable rules.
The interruption is significant because Bitget has been expanding its traditional-market infrastructure while simultaneously offering several different types of equity exposure. The company recently integrated official Nasdaq market data into its stock-related infrastructure, illustrating how crypto platforms increasingly depend on conventional securities-market data and execution providers even when the product is presented inside a crypto-style interface.
That dependency becomes particularly visible outside normal U.S. market hours. A platform can advertise extended or continuous access, but the actual ability to execute still depends on the venues providing liquidity during those sessions.
Alpaca Kept Whole-Share Trading Running Through Other Venues
Alpaca disclosed a more detailed picture of what happened behind the scenes.
The brokerage infrastructure provider said Blue Ocean ATS declared an exchange-wide halt at 11:46 p.m. ET because of network connectivity problems at its provider. As a result, Blue Ocean market data and Alpaca’s related overnight feeds became unavailable or stale.
Alpaca temporarily disabled overnight fractional and notional share orders because it could no longer reliably price or trigger certain transactions using the affected data.
Whole-share orders, however, remained available.
The reason was routing diversification. Alpaca said those orders could continue through multiple alternative trading systems rather than relying exclusively on Blue Ocean.
That difference is important. The outage did not simply divide affected platforms into “working” and “not working.” It exposed different levels of dependency within the same platform. Fractional orders were sufficiently dependent on Blue Ocean-linked market data that they had to be switched off, while whole-share execution had alternative routes available.
According to Blue Ocean ATS’s SEC filing, BOATS operates an automated electronic limit-order book for U.S. National Market System stocks, with its overnight trading session running from 8:00 p.m. to 4:00 a.m. Eastern Time.
Alpaca said overnight data resumed and fractional-share functionality was restored at 02:43 a.m. ET on October 21.
Binance Changed Equity-Perpetual Funding Instead of Halting Trading
Binance disclosed a third type of impact.
The exchange said one of the largest U.S. overnight alternative trading systems experienced intermittent network connectivity problems between 03:46 UTC and 06:30 UTC.
Binance did not identify the venue.
However, that window precisely overlaps Blue Ocean’s reported halt, which began at approximately 03:46 UTC and ended when trading resumed at 06:30 UTC. Bitget and Alpaca both explicitly identified Blue Ocean in their own disclosures.
The timing makes Blue Ocean a plausible explanation for Binance’s announcement, but the identity of Binance’s unnamed ATS cannot be stated as confirmed without disclosure from Binance or another directly involved party.
Binance’s response was also structurally different. Rather than announcing that its U.S. equity-linked perpetual contracts had stopped trading, the exchange said the affected premium-index data would be excluded from the 08:00 UTC funding-rate calculation for TradFi perpetual contracts whose underlying assets were U.S. equities.
This matters because perpetual futures use reference-price and funding mechanisms rather than direct ownership of the underlying shares. Binance has been rapidly developing multiple ways for crypto users to trade U.S. equities, including direct securities, tokenized products and equity-linked perpetual futures.
The October 21 incident demonstrates that those products can inherit traditional-market infrastructure risks even when the product itself trades on crypto infrastructure around the clock.
One Outage Exposed Three Different Infrastructure Dependencies
The most interesting part of the Blue Ocean incident is not simply that an overnight trading venue went offline. It is what failed downstream.
Bitget depended on Blue Ocean sufficiently for overnight U.S. stock execution that it suspended the relevant session.
Alpaca had enough routing redundancy to continue executing whole-share orders, but its fractional-share product still relied on Blue Ocean-linked pricing and market data.
Binance, meanwhile, illustrates a completely different dependency. A crypto perpetual does not need Blue Ocean to execute the derivative trade itself. But if overnight U.S. stock prices contribute to the mechanism used to calculate a premium index or funding rate, disruption in the traditional market can propagate into the economics of a derivative trading somewhere else.
That is a deeper issue for the emerging 24/7 equity market.
Continuous trading is often presented as if extending trading hours removes the boundaries of the traditional stock market. In practice, it frequently does the opposite: it creates additional layers between the investor and the underlying share.
A conventional stock might sit underneath an overnight ATS, brokerage routing infrastructure, fractional-share engine, tokenized representation or leveraged perpetual contract. Each layer can depend on different market data, pricing methodologies, liquidity providers and fallback mechanisms.
The growth of tokenized equities as an onchain access layer makes that architecture increasingly relevant. The front end may operate continuously, while meaningful price discovery can still depend heavily on traditional venues and market hours.
Redundant Execution Is Not the Same as Redundant Pricing
Alpaca’s response provides perhaps the clearest lesson from the outage.
Its whole-share orders continued because they could be routed to multiple overnight venues. Fractional trading stopped because the necessary market-data dependency could not be replaced as easily.
That distinction matters far beyond Alpaca.
A trading platform may have several execution venues and still contain a single point of failure in its pricing, reference data, market-data normalization or risk systems. Likewise, a crypto exchange may run its own derivative matching engine without interruption while still depending on an external securities venue for the information needed to calculate funding or mark prices safely.
For investors, “24/7 trading” therefore should not automatically be interpreted as 24/7 independence from the underlying market.
The more useful questions are where the platform obtains overnight prices, how many execution venues it can access, what happens when one reference source disappears, and whether pricing methodologies automatically remove stale or unreliable data.
Binance’s decision to exclude the affected premium-index period rather than use potentially compromised reference information shows one approach to that problem. Alpaca’s ability to preserve whole-share trading through other ATSs shows another.
Bitget’s broader suspension demonstrates what happens when the affected venue sits more directly in the critical execution path.
The Blue Ocean outage lasted less than three hours, but it provided an unusually clear stress test of the rapidly expanding overnight U.S. equity ecosystem. The same infrastructure failure reached spot stocks, fractional shares, tokenized equity products and crypto perpetual-futures funding in different ways.
That is likely to become more important as exchanges and fintech platforms compete to make U.S. equities appear continuously tradable. Extending the clock is relatively easy to market. Building enough execution, pricing and data redundancy to make that access genuinely resilient is the harder part.
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. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574