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.

Not sure who to compare?Start from who leads, then compareThe ranked answer per chain, with the figures that produced it.

Providers on Ethereum

Side by side

30d window · 3.0 days observed · generated 2026-08-27 20:46:29 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyNodeRealMerkle
Rank1246
Score99.497.187.578.4
StatusExcellentExcellentGoodGood
Availability99.98%99.97%99.84%99.98%
p50 latency19.4 ms19.8 ms87.4 ms107.0 ms
p95 latency35.9 ms48.4 ms100.0 ms195.2 ms
p99 latency78.1 ms718.6 ms125.8 ms242.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.35 blocks0.49 blocks
Rate limited00018,745
Unsupported000227
Samples117,756116,840114,87027,089

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

+2.3points

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

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

PublicNodevsNodeReal

+11.9points

  • Latency+12.0
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsMerkle

+21.0points

  • Latency+21.0
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

Latency over time