Robinhood Chain's transaction batches stopped reaching Ethereum for two separate intervals totaling 14 minutes on Friday after a surge in Base activity filled Ethereum's temporary data-storage capacity. Ethereum blocks reached the 21-blob ceiling, while the blob base fee rose 27-fold in less than 30 minutes. Robinhood Chain's batch poster, identified by L2BEAT as address 0xDaa5…87F4, missed Ethereum postings for 8 minutes and 36 seconds and then for another 5 minutes and 24 seconds before quadrupling its fee bid. The chain continued producing blocks and processing direct user transactions, although software relying on Ethereum batch data or the sequencer feed would have detected a disruption. Arbitrum said Robinhood Chain experienced no downtime and attributed the delay to Ethereum's layer-1 blob-market conditions. Base was the principal source of the congestion, increasing its blob use from 222 to 593 in the comparison period and accelerating batch submissions after its blocks saw a sharp rise in transactions. Robinhood Chain remained Ethereum's largest blob buyer in both samples. The incident highlights the distinction between an optimistic rollup's local transaction execution and the later publication of batch data to Ethereum, which supports public reconstruction, challenge mechanisms and withdrawals to Ethereum. Robinhood has not published a technical account, and its documentation lists no status page.