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 06:47:06 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleCloudflare
Rank1568
Score99.478.370.151.7
StatusExcellentGoodDegradedDegraded
Availability99.98%99.98%100.00%23.14%
p50 latency17.8 ms103.3 ms104.9 ms12.9 ms
p95 latency30.5 ms116.6 ms192.8 ms68.8 ms
p99 latency54.9 ms144.1 ms268.8 ms141.7 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.41 blocks0.51 blocksno cohort
Rate limited0791,4650
Unsupported0018277
Samples9,4479,3672,0739,378

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.

PublicNodevsBlast API

+21.1points

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

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

PublicNodevsMerkle

+29.3points

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

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

PublicNodevsCloudflare

+47.7points

  • Availability+29.7
  • Latency+10.8
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +47.7, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.

Latency over time