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 13:42:10 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3468
Score88.382.870.248.8
StatusGoodGoodDegradedPoor
Availability99.94%100.00%100.00%23.16%
p50 latency33.7 ms87.8 ms108.8 ms15.9 ms
p95 latency73.0 ms99.6 ms200.3 ms91.9 ms
p99 latency173.5 ms123.7 ms230.9 ms133.3 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.35 blocks0.34 blocks0.48 blocksno cohort
Rate limited4201,45219
Unsupported0018269
Samples9,0909,0862,1729,250

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

+5.5points

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

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

dRPCvsMerkle

+18.1points

  • Latency+18.0
  • Head freshness+0.2
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+39.5points

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

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