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
MetricdRPCNodeRealBlast APICloudflare
Rank3458
Score86.882.578.649.9
StatusGoodGoodGoodPoor
Availability99.95%100.00%100.00%23.20%
p50 latency33.1 ms87.8 ms107.1 ms15.3 ms
p95 latency77.8 ms99.8 ms124.3 ms85.5 ms
p99 latency175.1 ms123.1 ms153.3 ms119.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.36 blocks0.34 blocks0.41 blocksno cohort
Rate limited45010819
Unsupported000257
Samples8,6828,6668,8208,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 dRPC, the highest scorer of those selected.

dRPCvsNodeReal

+4.3points

  • Latency+4.4
  • Availability0.0
  • Head freshness0.0
  • Correctness+0.0

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

dRPCvsBlast API

+8.2points

  • Latency+8.2
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+36.9points

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

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