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 19:43:29 UTC

Selected providers compared across every measured metric
MetricdRPCMEV Blocker1RPCCloudflare
Rank3789
Score91.076.858.053.6
StatusExcellentGoodDegradedDegraded
Availability99.94%99.93%74.55%23.16%
p50 latency33.7 ms121.2 ms2024.4 ms15.1 ms
p95 latency70.8 ms212.7 ms6590.4 ms86.1 ms
p99 latency175.6 ms235.0 ms9196.2 ms249.2 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.37 blocks0.40 blocks0.95 blocksno cohort
Rate limited13336,59636
Unsupported0001,130
Samples37,81138,3557,91538,455

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.

dRPCvsMEV Blocker

+14.1points

  • Latency+14.1
  • Head freshness+0.0
  • Correctness0.0
  • Availability+0.0

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

dRPCvs1RPC

+32.9points

  • Latency+21.4
  • Availability+10.2
  • Head freshness+0.7
  • Correctness+0.7

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

dRPCvsCloudflare

+37.4points

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

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