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 17:33:37 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3458
Score89.682.978.345.9
StatusGoodGoodGoodPoor
Availability99.95%100.00%99.99%23.12%
p50 latency34.6 ms87.5 ms109.0 ms17.7 ms
p95 latency68.4 ms99.5 ms127.4 ms106.9 ms
p99 latency177.3 ms127.8 ms154.5 ms262.0 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.36 blocks0.33 blocks0.41 blocksno cohort
Rate limited230390
Unsupported000268
Samples8,8568,8548,9899,025

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

+6.7points

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

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

dRPCvsBlast API

+11.3points

  • Latency+11.2
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

dRPCvsCloudflare

+43.7points

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

The parts add to +43.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