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.4 days observed · generated 2026-08-27 06:10:19 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3679
Score93.078.877.955.5
StatusExcellentGoodGoodDegraded
Availability99.93%99.98%99.89%23.10%
p50 latency33.9 ms106.5 ms118.4 ms15.0 ms
p95 latency71.9 ms195.8 ms209.2 ms87.7 ms
p99 latency167.7 ms244.4 ms232.7 ms253.1 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.36 blocks0.47 blocks0.40 blocksno cohort
Rate limited58414,988277
Unsupported018202,739
Samples91,63721,53993,00992,987

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.

dRPCvsMerkle

+14.2points

  • Latency+14.1
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+15.1points

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

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

dRPCvsCloudflare

+37.5points

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

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