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

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3458
Score88.380.178.050.6
StatusGoodGoodGoodDegraded
Availability99.94%100.00%99.99%23.08%
p50 latency31.4 ms87.7 ms104.8 ms13.3 ms
p95 latency64.1 ms106.1 ms120.2 ms74.6 ms
p99 latency158.1 ms142.6 ms147.3 ms116.8 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.36 blocks0.36 blocks0.42 blocksno cohort
Rate limited3701137
Unsupported000252
Samples8,3108,3268,4348,465

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

+8.1points

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

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

dRPCvsBlast API

+10.2points

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

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