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 09:13:39 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3459
Score90.786.483.852.8
StatusExcellentGoodGoodDegraded
Availability99.91%100.00%99.99%23.12%
p50 latency34.2 ms87.2 ms105.3 ms15.6 ms
p95 latency71.1 ms100.3 ms122.4 ms89.5 ms
p99 latency176.6 ms128.9 ms146.1 ms239.9 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.38 blocks0.34 blocks0.42 blocksno cohort
Rate limited154035143
Unsupported0001,106
Samples37,01037,01637,39437,566

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

  • Latency+4.3
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

dRPCvsBlast API

+6.9points

  • Latency+6.8
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

dRPCvsCloudflare

+37.9points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+0.9

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