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

30d window · 2.6 days observed · generated 2026-08-27 11:16:50 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMEV BlockerCloudflare
Rank1279
Score99.495.577.755.2
StatusExcellentExcellentGoodDegraded
Availability99.97%99.96%99.89%23.11%
p50 latency18.5 ms19.8 ms118.6 ms15.0 ms
p95 latency33.8 ms57.0 ms209.4 ms86.6 ms
p99 latency71.7 ms802.3 ms232.7 ms251.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.40 blocksno cohort
Rate limited00396
Unsupported0002,982
Samples102,222101,445101,267101,270

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

PublicNodevsTenderly

+3.9points

  • Latency+3.9
  • Head freshness+0.0
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.6points

  • Latency+21.7
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+44.2points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency+7.3
  • Correctness2.2

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