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-26 21:10:42 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCCloudflare
Rank1239
Score99.498.691.552.3
StatusExcellentExcellentExcellentDegraded
Availability99.98%99.96%99.94%23.10%
p50 latency18.8 ms19.8 ms34.1 ms16.0 ms
p95 latency34.3 ms37.9 ms67.9 ms94.4 ms
p99 latency71.3 ms303.3 ms165.4 ms246.7 ms
Correctness99.99%99.98%99.99%100.00%
Head lag0.49 blocks0.49 blocks0.37 blocksno cohort
Rate limited0011239
Unsupported0001,108
Samples37,84737,58936,96537,457

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

  • Latency+0.7
  • Availability+0.0
  • Correctness+0.0
  • Head freshness+0.0

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

PublicNodevsdRPC

+7.9points

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

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