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

24h window · 24 hours observed · generated 2026-08-27 06:19:38 UTC

Selected providers compared across every measured metric
MetricNodeRealMerkleMEV BlockerCloudflare
Rank4679
Score86.577.976.952.3
StatusGoodGoodGoodDegraded
Availability100.00%100.00%99.90%23.13%
p50 latency87.1 ms107.2 ms119.8 ms16.0 ms
p95 latency99.9 ms193.6 ms210.1 ms92.8 ms
p99 latency126.4 ms240.0 ms233.6 ms244.6 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.34 blocks0.49 blocks0.40 blocksno cohort
Rate limited06,026236
Unsupported07301,114
Samples37,1788,62337,71837,728

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

+8.5points

  • Latency+8.4
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

NodeRealvsMEV Blocker

+9.5points

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

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

NodeRealvsCloudflare

+34.2points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency2.9
  • Correctness2.2

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