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-27 08:30:41 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV Blocker1RPC
Rank3679
Score88.170.069.50.0
StatusGoodDegradedDegradedPoor
Availability99.95%100.00%99.92%0.00%
p50 latency31.3 ms104.8 ms119.2 ms0.0 ms
p95 latency63.1 ms192.8 ms207.8 ms0.0 ms
p99 latency158.5 ms251.0 ms226.1 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.37 blocks0.62 blocks0.42 blocksno cohort
Rate limited321,41011,538
Unsupported01500
Samples8,7702,0118,9051,761

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

+18.1points

  • Latency+17.8
  • Head freshness+0.3
  • Availability0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+18.7points

  • Latency+18.6
  • Head freshness+0.1
  • Availability+0.0
  • Correctness0.0

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

dRPCvs1RPC

+88.1points

  • Availability+40.0
  • Correctness*+20.0
  • Latency*+18.6
  • Head freshness*+9.5

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