Skip to content

Providers

Compare RPC providers on measured data

The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.

Providers on Ethereum

Side by side

6h window · 6.0 hours observed · generated 2026-08-27 12:26:37 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank4678
Score82.570.069.549.9
StatusGoodDegradedDegradedPoor
Availability100.00%100.00%99.93%23.20%
p50 latency87.8 ms106.8 ms122.8 ms15.3 ms
p95 latency99.8 ms202.1 ms212.2 ms85.5 ms
p99 latency123.1 ms231.3 ms234.0 ms119.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.34 blocks0.50 blocks0.40 blocksno cohort
Rate limited01,426119
Unsupported0170257
Samples8,6662,0908,8068,822

9 providers scored against each other.

Where the gap comes from

Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against NodeReal, the highest scorer of those selected.

NodeRealvsMerkle

+12.6points

  • Latency+12.4
  • Head freshness+0.2
  • Availability+0.0
  • Correctness+0.0

The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.

NodeRealvsMEV Blocker

+13.0points

  • Latency+12.9
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

The parts add to +13.0, exactly — the score is a weighted sum, so it comes apart.

NodeRealvsCloudflare

+32.6points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency4.5
  • Correctness2.2

The parts add to +32.6, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.

Latency over time