Ankr Ethereum WebSocket Connection Failures Across ORD, NRT, and EWR
On July 3, 2026, QuantLoop observed Ankr Ethereum WebSocket connection failures from its ORD, NRT, and EWR probes. The affected probes detected silent newHeads streams, disconnected, and remained in a reconnect/error loop until recovery.
Summary
QuantLoop classifies this as a provider-path WebSocket connectivity incident. The affected ORD, NRT, and EWR probes were unable to re-establish working Ankr Ethereum WebSocket connections after detecting silent streams.
During the affected window, the affected probes missed 322 Ethereum blocks in real time, from block 25,451,399 through 25,451,720.
Timeline
Times are shown in UTC. This timeline describes QuantLoop probe observations. No matching provider-reported Ankr incident was identified at the time of publication.
- 2026-07-03 06:31:30ZQuantLoop detects silent Ankr newHeads streamsQuantLoop's ORD, NRT, and EWR probes detected silent Ankr Ethereum
newHeadsstreams after receiving no stream update for 60 seconds. The last block observed before the affected window was25,451,398. - 2026-07-03 06:31:30ZAffected probes disconnect and begin recoveryAfter detecting silent streams, the affected probes disconnected and attempted to reconnect to Ankr's Ethereum WebSocket endpoint.
- 2026-07-03 06:31:30Z - 07:35:06ZReconnect/error loopThe affected probes remained stuck in a reconnect/error loop. Reconnect attempts failed after connection retries were exceeded.
- 2026-07-03 07:35:06ZWebSocket recovery observedQuantLoop's affected probes resumed receiving Ethereum
newHeadsupdates from Ankr. The next block observed after recovery was25,451,721.
Observed impact
The affected probes were unable to collect live Ethereum newHeads observations from Ankr for approximately 64 minutes.
| Affected probes | ORD / NRT / EWR |
|---|---|
| Last block seen before incident | 25,451,398 |
| Next block seen after recovery | 25,451,721 |
| Blocks not observed in real time | 25,451,399 - 25,451,720 |
| Missing real-time observations | 322 blocks |
Interpretation
The affected observers were unable to establish working connections to Ankr's Ethereum WebSocket endpoint. While the reconnect loop was active, those observers could not subscribe to or receive real-time Ethereum stream data from Ankr.
Five other QuantLoop probes remained healthy against the same Ankr Ethereum WebSocket endpoint during the same window. For that reason, QuantLoop classifies this as a provider-path WebSocket connectivity incident, not a global Ankr Ethereum outage.
For real-time systems, this matters. Provider availability is not one universal state: some paths can keep receiving live data while another path cannot establish or maintain a working WebSocket stream.
This is the broader monitoring gap discussed in 99.99% Uptime Does Not Mean 99.99% Data Delivery: real-time systems need to measure stream connectivity, silence, missed updates, and recovery behavior, not just generic endpoint availability.
External status reference
No matching provider-reported Ankr incident was identified at the time of publication. This incident note is based on QuantLoop probe observations and describes externally observed Ethereum WebSocket connectivity and block visibility from monitored vantage points.
View Ankr RPC health page