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

24h window · 24 hours observed · generated 2026-08-27 17:52:48 UTC

Selected providers compared across every measured metric
MetricNodeRealMEV Blocker1RPCCloudflare
Rank4789
Score86.776.957.853.5
StatusGoodGoodDegradedDegraded
Availability100.00%99.93%73.97%23.15%
p50 latency87.3 ms121.2 ms2024.4 ms15.1 ms
p95 latency100.0 ms212.5 ms6590.4 ms87.0 ms
p99 latency129.8 ms235.6 ms9196.2 ms242.6 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.34 blocks0.40 blocks0.95 blocksno cohort
Rate limited036,63636
Unsupported0001,137
Samples38,05638,6097,96238,705

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

+9.7points

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

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

NodeRealvs1RPC

+28.9points

  • Latency+17.1
  • Availability+10.4
  • Head freshness+0.7
  • Correctness+0.7

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

NodeRealvsCloudflare

+33.2points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency3.9
  • Correctness2.2

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