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 10:38:01 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3679
Score90.577.876.852.8
StatusExcellentGoodGoodDegraded
Availability99.91%100.00%99.92%23.12%
p50 latency34.2 ms107.1 ms120.2 ms15.5 ms
p95 latency72.2 ms193.3 ms210.5 ms89.1 ms
p99 latency175.5 ms237.9 ms232.4 ms229.3 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.38 blocks0.51 blocks0.40 blocksno cohort
Rate limited1646,115355
Unsupported07601,123
Samples37,6638,77338,22238,219

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.7points

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

The parts add to +12.7, 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.6points

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

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