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

7d window · 44 hours observed · generated 2026-08-26 16:19:52 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank3679
Score88.578.477.555.6
StatusGoodGoodGoodDegraded
Availability99.74%99.97%99.87%23.09%
p50 latency87.5 ms106.5 ms118.1 ms15.3 ms
p95 latency100.0 ms196.9 ms208.7 ms89.3 ms
p99 latency123.7 ms245.5 ms233.0 ms255.6 ms
Correctness99.99%100.00%99.98%100.00%
Head lag0.35 blocks0.47 blocks0.39 blocksno cohort
Rate limited011,483041
Unsupported014002,081
Samples69,54716,53070,62270,617

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

+10.2points

  • Latency+10.1
  • Head freshness+0.1
  • Availability0.1
  • Correctness0.0

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

NodeRealvsMEV Blocker

+11.0points

  • Latency+11.0
  • Head freshness+0.1
  • Availability0.1
  • Correctness+0.0

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

NodeRealvsCloudflare

+33.0points

  • Availability+29.6
  • Head freshness*+9.6
  • Latency4.0
  • Correctness2.2

The parts add to +33.0, 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