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

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3459
Score91.586.684.252.3
StatusExcellentGoodGoodDegraded
Availability99.94%100.00%99.98%23.10%
p50 latency34.1 ms87.4 ms104.1 ms16.0 ms
p95 latency67.9 ms100.1 ms120.6 ms94.4 ms
p99 latency165.4 ms124.8 ms138.3 ms246.7 ms
Correctness99.99%100.00%99.98%100.00%
Head lag0.37 blocks0.35 blocks0.42 blocksno cohort
Rate limited112036339
Unsupported0001,108
Samples36,96536,92737,38437,457

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

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

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

dRPCvsBlast API

+7.3points

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

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

dRPCvsCloudflare

+39.2points

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

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