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-27 00:28:06 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCBlast API
Rank1235
Score99.499.091.384.1
StatusExcellentExcellentExcellentGood
Availability99.98%99.98%99.92%99.98%
p50 latency18.4 ms19.8 ms34.1 ms104.3 ms
p95 latency35.0 ms37.0 ms68.6 ms121.0 ms
p99 latency73.4 ms236.2 ms169.0 ms140.6 ms
Correctness100.00%99.99%99.99%99.99%
Head lag0.49 blocks0.49 blocks0.37 blocks0.42 blocks
Rate limited00125406
Unsupported0000
Samples38,31638,01337,40737,805

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

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

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

PublicNodevsdRPC

+8.1points

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

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

PublicNodevsBlast API

+15.3points

  • Latency+15.4
  • Head freshness0.1
  • Correctness+0.0
  • Availability0.0

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

Latency over time