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

6h window · 6.0 hours observed · generated 2026-08-27 09:46:09 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMEV BlockerCloudflare
Rank1278
Score99.499.269.550.3
StatusExcellentExcellentDegradedDegraded
Availability99.98%99.95%99.91%23.09%
p50 latency19.4 ms18.7 ms119.8 ms13.5 ms
p95 latency32.8 ms33.3 ms208.7 ms77.1 ms
p99 latency68.6 ms123.2 ms226.2 ms116.5 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.49 blocks0.42 blocksno cohort
Rate limited00119
Unsupported000278
Samples9,4109,3339,3239,348

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.2points

  • Latency+0.2
  • Availability+0.0
  • Head freshness0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+29.9points

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

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

PublicNodevsCloudflare

+49.1points

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

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