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 17:52:11 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMerkleCloudflare
Rank4568
Score82.978.370.845.9
StatusGoodGoodDegradedPoor
Availability100.00%99.99%100.00%23.10%
p50 latency87.5 ms109.0 ms110.7 ms17.6 ms
p95 latency99.5 ms127.6 ms191.8 ms106.7 ms
p99 latency127.2 ms155.0 ms235.0 ms265.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.33 blocks0.41 blocks0.55 blocksno cohort
Rate limited0391,5100
Unsupported0020282
Samples9,3509,4902,2249,518

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.6points

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

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

NodeRealvsMerkle

+12.1points

  • Latency+11.8
  • Head freshness+0.3
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsCloudflare

+37.0points

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

The parts add to +37.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