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 13:55:21 UTC

Selected providers compared across every measured metric
MetricdRPCBlast API1RPCCloudflare
Rank3589
Score90.583.857.853.1
StatusExcellentGoodDegradedDegraded
Availability99.92%99.99%73.97%23.14%
p50 latency34.1 ms105.8 ms2024.4 ms15.2 ms
p95 latency72.1 ms122.5 ms6590.4 ms87.7 ms
p99 latency171.7 ms149.0 ms9196.2 ms218.2 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.37 blocks0.41 blocks0.95 blocksno cohort
Rate limited1583316,64555
Unsupported0001,137
Samples38,11938,5227,97738,700

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.

dRPCvsBlast API

+6.8points

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

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

dRPCvs1RPC

+32.7points

  • Latency+21.0
  • Availability+10.4
  • Correctness+0.7
  • Head freshness+0.7

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

dRPCvsCloudflare

+37.4points

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

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