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 19:27:20 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3679
Score91.077.976.953.6
StatusExcellentGoodGoodDegraded
Availability99.94%100.00%99.93%23.16%
p50 latency33.6 ms107.5 ms121.2 ms15.0 ms
p95 latency70.7 ms193.9 ms212.6 ms86.0 ms
p99 latency175.4 ms235.5 ms235.0 ms248.6 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.53 blocks0.40 blocksno cohort
Rate limited1335,988336
Unsupported07301,118
Samples37,3848,69537,91938,023

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

+13.1points

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

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

dRPCvsMEV Blocker

+14.1points

  • Latency+14.1
  • Head freshness+0.0
  • Correctness0.0
  • Availability+0.0

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

dRPCvsCloudflare

+37.4points

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

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