Robinhood Chain kept producing blocks through the outage reported on Friday. What stopped was its transaction data reaching Ethereum, for 14 minutes across two gaps.
Posting those batches is what puts Robinhood Chain's data where anyone can reconstruct the chain and check it, and what allows funds to leave for Ethereum. Robinhood Chain posts more of that data than any other network, so a delay in its batches is the largest single interruption the blob market can produce.
Arbitrum said Ethereum's blob market caused the delay. That fits the second gap, which began after the blob price rose past the ceiling Robinhood Chain's poster was bidding. It does not fit the first and longer one, which ran 8 minutes and 36 seconds while Ethereum blocks carried 263 unused blob slots and priced them at 0.0086 gwei against the poster's standing bid of 0.0616.
"Robinhood Chain experienced no downtime," Arbitrum posted at 2:19 p.m. New York time, after posts on X and two crypto outlets reported that the network had stopped producing blocks for around 14 minutes. "Earlier today, Robinhood Chain experienced batch posting delays due to L1 market blob behavior. Direct user transactions experienced no delays. Some infrastructure providers that rely on Robinhood Chain's data stream experienced a brief performance impact due to a high number of feed subscribers. Robinhood Chain remains operational." The post had drawn about 24,500 views, 314 likes and 40 replies within an hour.
