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 09:13:57 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score88.378.070.050.5
StatusGoodGoodDegradedDegraded
Availability99.94%99.99%100.00%23.09%
p50 latency31.4 ms104.8 ms105.3 ms13.3 ms
p95 latency64.0 ms120.2 ms194.3 ms74.8 ms
p99 latency158.0 ms147.4 ms228.0 ms116.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.42 blocks0.61 blocksno cohort
Rate limited371151,3317
Unsupported0014253
Samples8,3298,4551,9328,484

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

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

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

dRPCvsMerkle

+18.3points

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

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

dRPCvsCloudflare

+37.8points

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

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