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

7d window · 2.2 days observed · generated 2026-08-27 02:28:38 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APIMerkleCloudflare
Rank3569
Score93.686.079.156.0
StatusExcellentGoodGoodDegraded
Availability99.93%99.98%99.98%23.10%
p50 latency34.0 ms104.6 ms106.6 ms15.3 ms
p95 latency72.6 ms122.2 ms195.7 ms89.1 ms
p99 latency169.2 ms144.1 ms243.1 ms254.5 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.36 blocks0.42 blocks0.46 blocksno cohort
Rate limited56597314,06477
Unsupported001722,562
Samples85,75286,63420,23087,006

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

+7.6points

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

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

dRPCvsMerkle

+14.5points

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

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

dRPCvsCloudflare

+37.7points

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

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