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.7 days observed · generated 2026-08-27 14:19:05 UTC

Selected providers compared across every measured metric
MetricNodeRealMEV Blocker1RPCCloudflare
Rank4789
Score87.777.662.454.8
StatusGoodGoodDegradedDegraded
Availability99.83%99.89%84.99%23.11%
p50 latency87.4 ms118.9 ms225.7 ms15.1 ms
p95 latency100.1 ms209.7 ms4391.3 ms87.5 ms
p99 latency126.0 ms233.3 ms7602.5 ms250.8 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.35 blocks0.40 blocks0.91 blocksno cohort
Rate limited0318,26096
Unsupported0003,127
Samples104,582106,18022,327106,206

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 NodeReal, the highest scorer of those selected.

NodeRealvsMEV Blocker

+10.1points

  • Latency+10.1
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

NodeRealvs1RPC

+25.3points

  • Latency+18.2
  • Availability+5.9
  • Head freshness+0.7
  • Correctness+0.5

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

NodeRealvsCloudflare

+33.0points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency4.0
  • Correctness2.2

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