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 08:35:03 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyNodeRealMerkle
Rank1246
Score99.498.880.170.0
StatusExcellentExcellentGoodDegraded
Availability99.99%99.98%100.00%100.00%
p50 latency18.3 ms18.4 ms87.7 ms104.7 ms
p95 latency30.3 ms32.2 ms105.0 ms192.8 ms
p99 latency61.4 ms82.4 ms139.7 ms251.0 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.48 blocks0.36 blocks0.62 blocks
Rate limited0001,417
Unsupported00015
Samples9,1179,0318,9142,026

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

  • Latency+0.6
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsNodeReal

+19.4points

  • Latency+19.5
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+29.4points

  • Latency+29.2
  • Head freshness+0.2
  • Availability0.0
  • Correctness+0.0

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

Latency over time