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 08:05:16 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score88.377.970.051.0
StatusGoodGoodDegradedDegraded
Availability99.95%99.99%100.00%23.12%
p50 latency31.1 ms104.1 ms104.5 ms13.0 ms
p95 latency61.7 ms118.6 ms192.8 ms70.5 ms
p99 latency156.4 ms145.2 ms268.8 ms122.2 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.37 blocks0.42 blocks0.60 blocksno cohort
Rate limited30901,2940
Unsupported0013246
Samples8,0908,2281,8458,241

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

+10.4points

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

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

dRPCvsMerkle

+18.2points

  • Latency+18.0
  • Head freshness+0.3
  • Availability0.0
  • Correctness0.0

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