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.9 days observed · generated 2026-08-27 19:10:43 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMerkleMEV Blocker
Rank1267
Score99.496.978.477.5
StatusExcellentExcellentGoodGood
Availability99.98%99.96%99.98%99.89%
p50 latency19.3 ms19.8 ms107.0 ms119.2 ms
p95 latency35.6 ms49.4 ms195.7 ms210.4 ms
p99 latency76.4 ms729.4 ms242.7 ms234.0 ms
Correctness99.99%99.99%100.00%99.99%
Head lag0.49 blocks0.50 blocks0.48 blocks0.40 blocks
Rate limited0018,3353
Unsupported002240
Samples115,144114,26126,482114,037

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

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

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

PublicNodevsMerkle

+21.0points

  • Latency+21.0
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.9points

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

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

Latency over time