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-26 20:07:17 UTC

Selected providers compared across every measured metric
MetricdRPCBlast API1RPCCloudflare
Rank3589
Score91.584.264.452.4
StatusExcellentGoodDegradedDegraded
Availability99.94%99.97%89.75%23.10%
p50 latency34.0 ms104.0 ms259.6 ms15.9 ms
p95 latency67.5 ms120.3 ms2579.7 ms93.5 ms
p99 latency166.3 ms138.3 ms4625.5 ms246.3 ms
Correctness99.99%99.98%98.18%100.00%
Head lag0.37 blocks0.42 blocks0.94 blocksno cohort
Rate limited1093636,43428
Unsupported0001,108
Samples36,87537,2967,70637,379

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

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

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

dRPCvs1RPC

+27.1points

  • Latency+22.0
  • Availability+4.1
  • Head freshness+0.7
  • Correctness+0.4

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

dRPCvsCloudflare

+39.1points

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

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