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 00:34:56 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score90.483.977.755.4
StatusExcellentGoodGoodDegraded
Availability99.94%100.00%100.00%23.29%
p50 latency33.7 ms103.2 ms102.7 ms11.6 ms
p95 latency67.6 ms114.3 ms191.0 ms69.5 ms
p99 latency172.2 ms123.7 ms219.4 ms246.1 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.37 blocks0.42 blocks0.40 blocksno cohort
Rate limited5352276
Unsupported00245
Samples1,5861,6153401,618

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

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

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

dRPCvsMerkle

+12.6points

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

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

dRPCvsCloudflare

+35.0points

  • Availability+29.6
  • Head freshness*+9.5
  • Correctness2.2
  • Latency1.9

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