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.3 days observed · generated 2026-08-27 04:42:32 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMEV BlockerCloudflare
Rank3479
Score93.288.678.055.6
StatusExcellentGoodGoodDegraded
Availability99.93%99.79%99.89%23.11%
p50 latency33.9 ms87.3 ms118.5 ms15.1 ms
p95 latency72.3 ms99.8 ms209.3 ms88.3 ms
p99 latency168.7 ms123.1 ms232.9 ms253.7 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.36 blocks0.35 blocks0.40 blocksno cohort
Rate limited5770277
Unsupported0002,669
Samples89,31089,26690,63690,619

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.

dRPCvsNodeReal

+4.6points

  • Latency+4.6
  • Availability+0.1
  • Head freshness0.0
  • Correctness+0.0

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

dRPCvsMEV Blocker

+15.2points

  • Latency+15.1
  • Head freshness+0.0
  • Availability+0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+37.6points

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

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