Base, the Coinbase-backed Ethereum layer-2 network, says it has patched the bug responsible for back-to-back blockchain outages on June 25 and June 26, 2026. The fix followed two chain stalls
Base, the Coinbase-backed Ethereum layer-2 network, says it has patched the bug responsible for back-to-back blockchain outages on June 25 and June 26, 2026. The fix followed two chain stalls that halted block production and disrupted transactions for hours, prompting Base leader Jesse Pollak to confirm the root cause had been identified and resolved.
On June 25, Base's mainnet stopped producing new blocks after an invalid block created a consensus failure at block 47,806,542. The disruption halted block production and transaction processing for roughly two hours before the network resumed. For related coverage, see Polymarket Advertising Investigation: What WSJ Report Says.
Stalled Block Height 47,806,542 The official Base status page says the invalid block consensus problem stopped new block creation after block 47806542.The following day, June 26, Base reported a second mainnet chain stall at 15:33 UTC and noted it displayed "similar symptoms" to the previous incident. Block production resumed at 15:47 UTC, and the team moved the incident to monitoring at 16:11 UTC after implementing a fix. For related coverage, see Binance Says It Will Stay in the EU and Seek a License.
Base resolved the June 26 incident at 20:03 UTC and said a detailed postmortem would be published. The network had previously resumed operations after the initial two-hour outage on June 25, but the recurrence underscored that the first recovery had not fully eliminated the underlying problem. For related coverage, see Grant Cardone Says Cardone Capital Is Adding 282 BTC to Its Bitcoin Holdings.
Pollak addressed the situation directly on X, stating that the team had identified and patched the root cause and that all funds were safe throughout both incidents.
re: the chain halt today, the team has identified and patched the root cause and a full post-mortem is coming. all funds are/were safe. but a halt is not okay and we'll use this to continue to level up base as a platform for global, 24/7 finance. thank you for your patience.
— jesse.base.eth (@jessepollak) June 26, 2026
Source: @jessepollak on X
Base has not yet published the promised postmortem, so the exact technical root cause and whether one bug explains both consecutive halts is still not fully documented. The status page described the second stall as having "similar symptoms," but that language stops short of confirming the same bug caused both events.
The two-hour block production halt on June 25 meant no transactions could be confirmed on Base during that window. For users, this translated to stuck transfers, frozen decentralized app activity, and uncertainty about pending operations.
A second stall less than 24 hours later compounded the concern. Even though the June 26 disruption lasted a shorter period, the repetition raised questions about whether the network could reliably support the payments and tokenized asset use cases Coinbase has been positioning around.
Despite the consecutive incidents, Base's public status page shows 99.5% mainnet uptime over the past 90 days, suggesting the outages, while notable, remain statistical outliers against the network's broader operating record.
Base 90-Day Uptime 99.5% Base's own uptime panel shows 99.5% mainnet uptime over the last 90 days despite the two consecutive chain stalls.Broader market sentiment offers little cushion. The Fear & Greed Index sits at 18, firmly in "Extreme Fear" territory, meaning any reliability hiccup on a major layer-2 lands in an already risk-averse environment.
A patch announcement does not close the book on an infrastructure incident. The key signal is sustained uptime in the days and weeks ahead, particularly whether any further chain stalls surface with the same consensus failure pattern.
The pending postmortem is the most important follow-up. Until Base publishes the full technical breakdown, developers and node operators lack the detail needed to independently assess the fix's completeness. Base has already advised node operators to restart their nodes, a step that suggests the patch requires active adoption across the validator set.
Pollak's acknowledgment that "a halt is not okay" sets a clear accountability marker. For a network positioning itself as infrastructure for "global, 24/7 finance," consecutive outages, even brief ones, test that narrative directly. Whether the postmortem arrives promptly and whether uptime holds steady will determine how quickly the incident fades from the conversation.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
Read original article on tokentopnews.com
