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

6h window · 6.0 hours observed · generated 2026-08-26 22:28:43 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3678
Score86.370.769.547.0
StatusGoodDegradedDegradedPoor
Availability99.86%100.00%99.94%23.16%
p50 latency35.5 ms108.2 ms123.3 ms16.9 ms
p95 latency78.3 ms192.3 ms213.7 ms97.6 ms
p99 latency192.3 ms234.1 ms239.1 ms250.0 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.39 blocks0.42 blocks0.41 blocksno cohort
Rate limited391,364030
Unsupported0150262
Samples8,7151,9798,8728,809

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

+15.6points

  • Latency+15.6
  • Availability0.1
  • Head freshness+0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+16.8points

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

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

dRPCvsCloudflare

+39.3points

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

The parts add to +39.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