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 16:44:28 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score82.978.470.546.5
StatusGoodGoodDegradedPoor
Availability100.00%99.99%100.00%23.14%
p50 latency87.4 ms108.8 ms110.2 ms17.4 ms
p95 latency99.5 ms127.6 ms197.2 ms103.8 ms
p99 latency130.3 ms155.0 ms256.1 ms253.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.34 blocks0.42 blocks0.51 blocksno cohort
Rate limited0591,4840
Unsupported0019275
Samples9,1349,2822,1629,313

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.

NodeRealvsBlast API

+4.5points

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

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

NodeRealvsMerkle

+12.4points

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

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

NodeRealvsCloudflare

+36.4points

  • Availability+29.7
  • Head freshness*+9.6
  • Correctness2.2
  • Latency0.6

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