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:44:25 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score89.978.369.551.5
StatusGoodGoodDegradedDegraded
Availability100.00%100.00%100.00%23.33%
p50 latency30.6 ms103.2 ms107.3 ms12.8 ms
p95 latency56.2 ms116.1 ms196.0 ms69.2 ms
p99 latency155.2 ms144.3 ms228.0 ms242.0 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.36 blocks0.41 blocks0.82 blocksno cohort
Rate limited6252600
Unsupported00148
Samples1,5751,5973571,608

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

+11.6points

  • Latency+11.5
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

dRPCvsMerkle

+20.4points

  • Latency+19.9
  • Head freshness+0.5
  • Availability+0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+38.4points

  • Availability+29.6
  • Head freshness*+9.6
  • Correctness2.2
  • Latency+1.4

The parts add to +38.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