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.4 days observed · generated 2026-08-27 05:39:23 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCCloudflare
Rank1239
Score99.494.793.055.5
StatusExcellentExcellentExcellentDegraded
Availability99.97%99.97%99.93%23.11%
p50 latency18.2 ms19.8 ms33.9 ms15.0 ms
p95 latency33.5 ms63.2 ms72.0 ms87.9 ms
p99 latency69.9 ms844.3 ms168.3 ms253.4 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.36 blocksno cohort
Rate limited0058277
Unsupported0002,714
Samples93,04892,33990,81492,154

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

+4.7points

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

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

PublicNodevsdRPC

+6.4points

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

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

PublicNodevsCloudflare

+43.9points

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

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