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 13:20:40 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3679
Score90.577.876.853.2
StatusExcellentGoodGoodDegraded
Availability99.92%100.00%99.92%23.14%
p50 latency34.1 ms107.0 ms120.6 ms15.1 ms
p95 latency72.4 ms193.9 ms211.3 ms87.1 ms
p99 latency172.2 ms235.0 ms232.5 ms211.7 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.38 blocks0.50 blocks0.40 blocksno cohort
Rate limited1565,984355
Unsupported07101,110
Samples37,1958,63837,74537,764

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

+12.6points

  • Latency+12.5
  • Head freshness+0.2
  • Availability0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+13.6points

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

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

dRPCvsCloudflare

+37.3points

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

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