dRPC Ethereum newHeads visibility loss observed from Los Angeles
On May 31, 2026, QuantLoop observed a temporary Ethereum newHeads visibility loss for dRPC from its Los Angeles probe. For approximately 20 minutes, the probe stopped receiving fresh Ethereum block headers from dRPC in real time.
Summary
On May 31, 2026, QuantLoop observed dRPC's Ethereum newHeads websocket stream stop delivering fresh block headers to the LAX probe for approximately 20 minutes.
QuantLoop classifies this as a provider-region block visibility event observed from a single monitoring location. The observed failure mode was a loss of live Ethereum head delivery from dRPC to the LAX probe.
No corresponding provider-reported outage was identified at the time of publication.
During the visibility gap, the affected probe did not observe 95 Ethereum blocks in real time: blocks 25,213,553 through 25,213,647. Header delivery resumed at block 25,213,648.
Timeline
Times are shown in UTC. This timeline reflects QuantLoop's observed visibility loss and recovery for dRPC from the Los Angeles probe.
- 2026-05-31 06:27:37ZQuantLoop detects dRPC newHeads visibility loss from Los AngelesQuantLoop's Los Angeles probe stopped receiving new Ethereum block headers from dRPC's websocket
newHeadsstream. - 2026-05-31 06:46:01ZQuantLoop observes dRPC newHeads recoveryQuantLoop's LAX probe started receiving new Ethereum block headers from dRPC again.
Interpretation
This event shows that a websocket connection can remain connected while no longer delivering fresh block headers.
For systems that react to new blocks, endpoint reachability is not enough. The endpoint also needs to expose the latest head when the rest of the monitored network sees it.
This is the distinction between RPC latency and block visibility latency: response speed measures how fast an endpoint answers, while visibility measures when new chain state becomes observable. QuantLoop explains this in RPC Latency vs Block Visibility Latency.
The observed pattern was limited to QuantLoop's Los Angeles probe for dRPC. It does not prove a global dRPC outage, and no corresponding provider-reported outage was identified at the time of publication.
This incident note is based on QuantLoop probe observations. It describes provider-path block visibility from a monitored vantage point, not provider-wide availability.