WeSearch

Coinbase's Base resumes block production after 2-hour outage

·2 min read · 0 reactions · 0 comments · 27 views
#coinbase#base#resumes#block#production
Coinbase's Base resumes block production after 2-hour outage
TL;DR · WeSearch summary

At 5:21 pm UTC the team said it “isolated a consensus problem that caused an invalid block to be sequenced. This prevented new blocks from being created.”Base said in an update just before 6 pm UTC that it had “recovered healthy blockbuilding” and that ecosystem-wide infrastructure was able to sync, adding it had identified the issue and would investigate the root cause and share a full post-mortem. Sui later said the downtime was caused by a network update that it knew had a low probability of causing a halt.Magazine: Bitcoin slides to $58K, XRP hits $1 but onchain data promising: Market MovesCointelegraph is committed to independent, transparent journalism.

Key facts
Original article
Cointelegraph.com News
Read full at Cointelegraph.com News →
Opening excerpt (first ~120 words) tap to expand

Written by Jesse Coghlanstaff editorReviewed by Felix Ngstaff editorWritten by Jesse Coghlanstaff editorReviewed by Felix Ngstaff editorCoinbase's Base resumes block production after 2-hour outageLatest NewsPublishedJun 26, 2026Coinbase's blockchain Base says a consensus problem knocked its network offline for around two hours on Thursday before it returned online.Base, the blockchain backed by crypto exchange Coinbase, has returned online after the network suffered nearly a two-hour outage due to a consensus issue that halted block production.Base posted to X on Thursday after the outage that the network’s blocks “are being produced normally, and we have verified widespread recovery in the ecosystem.”Base’s status page said it was investigating “unhealthy” block production at 4:03 pm UTC…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Cointelegraph.com News.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments