Loading prices…
🩸BEARISH

Base network resumes after two-hour outage from invalid block

It's the second major outage for the Coinbase-backed Ethereum layer-2 in under a year, and the root cause still hasn't been named, putting the network's reliability thesis back under the microscope.

Base network resumes after two-hour outage from invalid block
Base network resumes after two-hour outage from invalid block
Base network resumes after two-hour outage from invalid block
Base network resumes after two-hour outage from invalid block

Coinbase-backed Ethereum layer-2 network Base resumed block production Thursday after a roughly two-hour outage that halted the chain entirely. The first public indication of trouble came at 16:03 UTC, when the team reported that mainnet block production was "unhealthy." By 16:52 UTC, the team had identified a problem and was pursuing multiple remediation efforts, before the chain eventually came back online with internal nodes syncing correctly.

The Base team said an invalid block triggered the issue, though it has not yet disclosed whether the root cause was a software bug or a consensus-related fault. Ecosystem node operators were advised to restart their Base nodes to restore synchronization, and the team said it would continue monitoring network stability while the investigation runs.

Why it matters

The incident is the second major disruption for Base in under a year, following an earlier outage in August 2025. For a network positioning itself as the default consumer-grade layer-2 on Ethereum, repeat halts cut directly against the reliability argument that institutional and DeFi builders price in when picking where to deploy. Base has not yet published a post-mortem with a named cause, leaving node operators and integrators unable to independently assess whether this was a one-off or a class of bug.

Market impact

The two-hour window froze transaction processing on one of Ethereum's largest layer-2 networks by activity, an outsized share of consumer-facing flows. The disruption matters less for any single day's volume than for the signal it sends to the broader L2 competitive landscape, where Arbitrum, Optimism, and zkSync are actively courting the same cohort of builders and users. Watch for the post-mortem: whether Base names a software bug or a consensus fault will determine how seriously the rest of the rollup ecosystem treats this as a Base-specific event or a shared infrastructure risk.

Related tokens
$ETH

Frequently asked questions

  1. What happened to the Base network on Thursday?

    Base, Coinbase's Ethereum layer-2, halted block production for roughly two hours on Thursday after an invalid block triggered the issue. The team identified the problem by 16:52 UTC and the chain resumed with internal nodes syncing correctly.

  2. Did Base disclose the root cause of the outage?

    No. The Base team said an invalid block triggered the incident but has not yet said whether it stemmed from a software bug or a consensus-related fault. A post-mortem has not been published.

  3. Was this the first time Base went down?

    No. The Thursday outage follows a previous Base disruption in August 2025, making it the second major outage for the network in under a year.

  4. What did node operators need to do during the Base outage?

    The Base team advised ecosystem node operators to restart their Base nodes to restore synchronization once the chain resumed block production.

  5. Why does a Base outage matter for the broader Ethereum ecosystem?

    Base is one of Ethereum's largest layer-2 networks by activity, so a two-hour halt freezes a meaningful share of consumer-facing L2 flows. Repeat disruptions also weigh on Base's positioning versus competing rollups like Arbitrum, Optimism, and zkSync in the race for institutional and DeFi deployments.

Source attribution
Aggregated from CoinDesk · Verified · Last refreshed 1h ago
Open original →