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.1 days observed · generated 2026-08-26 23:38:50 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank2679
Score93.778.877.955.8
StatusExcellentGoodGoodDegraded
Availability99.93%99.98%99.88%23.10%
p50 latency34.1 ms106.7 ms118.5 ms15.4 ms
p95 latency72.7 ms196.1 ms209.4 ms90.4 ms
p99 latency169.3 ms243.2 ms233.5 ms255.1 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.36 blocks0.47 blocks0.40 blocksno cohort
Rate limited54813,320171
Unsupported016102,430
Samples81,23119,17682,46582,406

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

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

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

dRPCvsMEV Blocker

+15.8points

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

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

dRPCvsCloudflare

+38.0points

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

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