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

24h window · 24 hours observed · generated 2026-08-27 08:05:31 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score90.783.877.952.5
StatusExcellentGoodGoodDegraded
Availability99.92%99.99%100.00%23.13%
p50 latency34.2 ms105.1 ms107.2 ms15.8 ms
p95 latency70.8 ms122.2 ms193.5 ms91.1 ms
p99 latency173.0 ms145.2 ms240.0 ms242.3 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.38 blocks0.41 blocks0.50 blocksno cohort
Rate limited1443745,97536
Unsupported00711,102
Samples36,79437,1778,54737,341

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

  • Latency+6.9
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

dRPCvsMerkle

+12.8points

  • Latency+12.7
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

dRPCvsCloudflare

+38.2points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+1.2

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