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 10:50:00 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMEV Blocker1RPC
Rank3479
Score87.881.069.50.0
StatusGoodGoodDegradedPoor
Availability99.95%100.00%99.94%0.00%
p50 latency32.1 ms88.0 ms120.6 ms0.0 ms
p95 latency69.9 ms104.8 ms209.6 ms0.0 ms
p99 latency163.1 ms141.2 ms228.5 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.36 blocks0.35 blocks0.41 blocksno cohort
Rate limited46011,629
Unsupported0000
Samples9,2929,3009,4241,865

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.

dRPCvsNodeReal

+6.8points

  • Latency+6.9
  • Availability0.0
  • Head freshness0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+18.3points

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

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

dRPCvs1RPC

+87.8points

  • Availability+40.0
  • Correctness*+20.0
  • Latency*+18.2
  • Head freshness*+9.6

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