Robinhood Chain Blocks Kept Running While Data Failed to Reach Ethereum

Blocks Kept Coming, But Data Stopped Arriving

Robinhood Chain never stopped making blocks during the incident reported on Friday. What stopped was its transaction data reaching Ethereum. The data failed to arrive for exactly 14 minutes, split into two separate gaps.

Posting those data batches is how Robinhood Chain makes its records available for anyone to check and how it moves funds back to Ethereum. Because Robinhood Chain posts more data than any other network, delays in its batches create the biggest interruptions seen in the Ethereum blob market.

The blob market is where layer-2 blockchains publish their transaction data on Ethereum. It works like an auction where chains bid to have their data included in Ethereum blocks.

Key Numbers From the Incident

• Robinhood Chain produced 106,756 blocks between 12:00 and 15:00 UTC, averaging one every 101 milliseconds.
• The first gap lasted 8 minutes and 36 seconds, from 12:29:47 to 12:38:23 UTC.
• The second gap lasted 5 minutes and 24 seconds, from 12:42:47 to 12:48:11 UTC.
• During the first gap, 263 blob slots went unused across 29 Ethereum blocks.
• The blob base fee averaged 0.0086 gwei during the first gap, far below Robinhood Chain's standing bid of 0.0616 gwei.
• Base's transaction volume surged, with one block burning 360 million gas against a 400 million gas limit.

What Arbitrum Said About the Delay

Arbitrum posted at 2:19 p.m. New York time that Robinhood Chain experienced no downtime. The chain confirmed that blocks were still being produced and direct user transactions experienced no delays.

The post stated that batch posting delays occurred due to L1 market blob behavior. Some infrastructure providers that rely on Robinhood Chain's data stream experienced a brief performance impact due to a high number of feed subscribers.

Arbitrum blamed Ethereum's blob market for the delay. This explanation fits the second gap, which began after the blob price rose past the ceiling Robinhood Chain's poster was bidding. However, it does not explain the first and longer gap, where plenty of space was available at prices far below what Robinhood Chain had already offered.

Why the First Gap Remains Unclear

Data from Blobscan shows that Robinhood Chain's batch poster went nearly nine minutes without posting during the first gap. The poster had a standing bid of 0.0616 gwei, but the market base fee sat at just 0.0086 gwei. Over 260 slots remained unused during this time.

Blob price is not the only factor for inclusion. Transactions also compete on execution fees, and block builders sometimes carry fewer blobs than allowed to keep blocks moving quickly. However, neither of these factors explains 8 minutes and 36 seconds of absence across 263 open slots at a twelfth of the price the sender had already offered.

Robinhood has not published a technical account of the incident. Its chain documentation lists no status page. Whether the escalation in bidding that followed was a response to a rising market or a recovery from a fault in the poster itself is not established by the public record.

Base Demand Moved the Market

Robinson Chain's posting rate stayed steady throughout the day. But Base nearly tripled its blob usage, jumping from 222 blobs to 593 blobs over the same period. Arbitrum One also increased from 48 to 135 blobs. Total blob supply across all senders rose 59%.

Base submitted batches much more frequently during the crunch, posting one every 13 seconds at peak compared to once every 55 seconds in the morning. About 31% of sampled Base transactions in the affected window went to four unverified contracts that emit no event logs and move no tokens.

What Happens Next

The public record does not show a clear next step or announced timeline for fixes. Robinhood and Base did not reply to requests for comment by press time.

Sources

• The Defiant