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 05:27:29 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score89.178.269.850.9
StatusGoodGoodDegradedDegraded
Availability99.94%100.00%100.00%23.08%
p50 latency30.7 ms103.2 ms104.8 ms12.8 ms
p95 latency58.4 ms116.0 ms192.8 ms70.4 ms
p99 latency156.5 ms144.1 ms268.8 ms225.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.36 blocks0.42 blocks0.76 blocksno cohort
Rate limited4292490
Unsupported00147
Samples1,5751,6033591,604

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

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

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

dRPCvsMerkle

+19.3points

  • Latency+18.9
  • Head freshness+0.5
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+38.2points

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

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