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

30d window · 2.9 days observed · generated 2026-08-27 17:22:13 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3459
Score92.287.684.854.4
StatusExcellentGoodGoodDegraded
Availability99.93%99.83%99.98%23.11%
p50 latency33.8 ms87.4 ms105.1 ms15.2 ms
p95 latency71.7 ms100.0 ms122.6 ms88.7 ms
p99 latency169.3 ms126.1 ms147.4 ms251.8 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.36 blocks0.35 blocks0.42 blocksno cohort
Rate limited65001,19396
Unsupported0003,274
Samples109,486109,448110,755111,148

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

  • Latency+4.5
  • Availability+0.0
  • Head freshness0.0
  • Correctness0.0

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

dRPCvsBlast API

+7.3points

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

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

dRPCvsCloudflare

+37.7points

  • Availability+29.7
  • Head freshness*+9.6
  • Correctness2.2
  • Latency+0.7

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