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-26 22:04:01 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APIMerkle
Rank1356
Score99.491.384.178.0
StatusExcellentExcellentGoodGood
Availability99.98%99.93%99.98%100.00%
p50 latency18.7 ms34.1 ms104.1 ms107.0 ms
p95 latency34.7 ms68.5 ms120.9 ms196.0 ms
p99 latency72.1 ms168.4 ms140.3 ms241.2 ms
Correctness99.99%99.99%99.98%100.00%
Head lag0.49 blocks0.37 blocks0.42 blocks0.46 blocks
Rate limited01203566,002
Unsupported00078
Samples37,67136,78237,2008,676

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.

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.3
  • 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.

PublicNodevsMerkle

+21.4points

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

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

Latency over time