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-27 11:33:26 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealBlast APICloudflare
Rank3459
Score90.486.483.753.1
StatusExcellentGoodGoodDegraded
Availability99.91%100.00%99.99%23.14%
p50 latency34.2 ms87.2 ms105.5 ms15.4 ms
p95 latency72.5 ms100.1 ms122.9 ms87.4 ms
p99 latency172.8 ms128.3 ms147.8 ms194.1 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.38 blocks0.34 blocks0.41 blocksno cohort
Rate limited163034055
Unsupported0001,121
Samples37,54637,53837,93638,097

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

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

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

dRPCvsBlast API

+6.7points

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

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

dRPCvsCloudflare

+37.3points

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

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