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 12:03:54 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3568
Score86.978.669.850.0
StatusGoodGoodDegradedPoor
Availability99.96%100.00%100.00%23.18%
p50 latency33.2 ms107.0 ms106.6 ms15.1 ms
p95 latency77.5 ms124.0 ms203.3 ms85.3 ms
p99 latency176.2 ms153.4 ms231.3 ms117.3 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.36 blocks0.41 blocks0.52 blocksno cohort
Rate limited381081,33719
Unsupported0016240
Samples8,0768,2061,9488,210

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

+8.3points

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

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

dRPCvsMerkle

+17.1points

  • Latency+16.9
  • Head freshness+0.2
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+37.0points

  • Availability+29.7
  • Head freshness*+9.6
  • Correctness2.2
  • Latency0.1

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