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.6 days observed · generated 2026-08-27 11:44:44 UTC

Selected providers compared across every measured metric
MetricdRPCNodeReal1RPCCloudflare
Rank3489
Score92.487.962.555.1
StatusExcellentGoodDegradedDegraded
Availability99.93%99.82%85.27%23.11%
p50 latency33.8 ms87.4 ms225.7 ms15.0 ms
p95 latency72.1 ms100.1 ms4391.3 ms86.8 ms
p99 latency168.1 ms125.9 ms7602.5 ms250.9 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.36 blocks0.35 blocks0.91 blocksno cohort
Rate limited628017,54396
Unsupported0003,003
Samples100,521100,48921,502102,023

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.

dRPCvs1RPC

+29.9points

  • Latency+22.9
  • Availability+5.9
  • Head freshness+0.6
  • Correctness+0.5

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

dRPCvsCloudflare

+37.3points

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

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