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 09:43:07 UTC

Selected providers compared across every measured metric
MetricdRPCMEV Blocker1RPCCloudflare
Rank3789
Score90.677.058.252.8
StatusExcellentGoodDegradedDegraded
Availability99.91%99.92%74.93%23.12%
p50 latency34.2 ms120.1 ms2024.4 ms15.6 ms
p95 latency71.6 ms210.4 ms6590.4 ms89.3 ms
p99 latency176.3 ms231.8 ms9196.2 ms239.7 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.38 blocks0.40 blocks0.95 blocksno cohort
Rate limited15736,58655
Unsupported0001,128
Samples37,79638,3567,90138,356

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

+13.7points

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

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

dRPCvs1RPC

+32.4points

  • Latency+21.1
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.7

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

dRPCvsCloudflare

+37.8points

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

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