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 07:15:49 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMEV BlockerCloudflare
Rank1279
Score99.499.476.952.3
StatusExcellentExcellentGoodDegraded
Availability99.97%99.98%99.91%23.13%
p50 latency18.2 ms19.5 ms119.8 ms15.9 ms
p95 latency35.3 ms35.5 ms210.0 ms92.7 ms
p99 latency73.7 ms125.6 ms232.1 ms243.6 ms
Correctness100.00%99.99%99.99%100.00%
Head lag0.48 blocks0.49 blocks0.40 blocksno cohort
Rate limited00236
Unsupported0001,113
Samples37,98537,64537,61437,619

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

+0.0points

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

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

PublicNodevsMEV Blocker

+22.5points

  • Latency+22.6
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+47.1points

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

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