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.3 days observed · generated 2026-08-27 03:22:00 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMEV BlockerCloudflare
Rank1279
Score99.494.178.155.9
StatusExcellentExcellentGoodDegraded
Availability99.97%99.96%99.89%23.10%
p50 latency18.3 ms19.9 ms118.5 ms15.2 ms
p95 latency33.7 ms68.7 ms209.4 ms88.8 ms
p99 latency70.5 ms865.6 ms233.1 ms254.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.51 blocks0.40 blocksno cohort
Rate limited00277
Unsupported0002,603
Samples89,30488,63488,47888,443

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

+5.3points

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

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

PublicNodevsMEV Blocker

+21.3points

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

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

PublicNodevsCloudflare

+43.5points

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

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