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 14:59:29 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APICloudflare1RPC
Rank3589
Score88.178.448.00.0
StatusGoodGoodPoorPoor
Availability99.95%99.99%23.17%0.00%
p50 latency34.2 ms108.3 ms16.5 ms0.0 ms
p95 latency74.2 ms126.2 ms96.0 ms0.0 ms
p99 latency183.6 ms153.5 ms157.4 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.36 blocks0.41 blocksno cohortno cohort
Rate limited4071121,672
Unsupported002820
Samples9,5479,7049,7131,917

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

+9.7points

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

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

dRPCvsCloudflare

+40.1points

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

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

dRPCvs1RPC

+88.1points

  • Availability+40.0
  • Correctness*+20.0
  • Latency*+18.6
  • Head freshness*+9.6

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