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.2 days observed · generated 2026-08-27 01:35:41 UTC

Selected providers compared across every measured metric
MetricdRPCNodeReal1RPCCloudflare
Rank2489
Score93.889.162.656.1
StatusExcellentGoodDegradedDegraded
Availability99.93%99.78%85.50%23.10%
p50 latency34.1 ms87.4 ms225.7 ms15.3 ms
p95 latency72.6 ms99.9 ms4391.3 ms89.5 ms
p99 latency169.0 ms123.6 ms7602.5 ms254.7 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.36 blocks0.35 blocks0.91 blocksno cohort
Rate limited558014,70777
Unsupported0002,519
Samples84,34484,29818,25685,565

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

  • Latency+4.7
  • Availability+0.1
  • Head freshness0.0
  • Correctness0.0

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

dRPCvs1RPC

+31.2points

  • Latency+24.3
  • Availability+5.8
  • Head freshness+0.6
  • Correctness+0.5

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

dRPCvsCloudflare

+37.8points

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

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