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

1h window · 60 minutes observed · generated 2026-08-27 12:25:04 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3458
Score86.683.078.247.7
StatusGoodGoodGoodPoor
Availability99.94%100.00%100.00%23.37%
p50 latency34.0 ms87.3 ms108.4 ms16.9 ms
p95 latency80.5 ms98.8 ms128.6 ms97.9 ms
p99 latency193.6 ms120.9 ms158.8 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.38 blocks0.32 blocks0.41 blocksno cohort
Rate limited100100
Unsupported00045
Samples1,5731,5651,5961,593

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

+3.6points

  • Latency+3.7
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

dRPCvsBlast API

+8.4points

  • Latency+8.4
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+38.9points

  • Availability+29.6
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+2.0

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