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 17:18:07 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleCloudflare
Rank2568
Score95.178.371.146.1
StatusExcellentGoodDegradedPoor
Availability100.00%99.99%100.00%23.10%
p50 latency25.5 ms109.0 ms110.0 ms17.6 ms
p95 latency50.0 ms127.5 ms188.4 ms104.9 ms
p99 latency112.4 ms154.5 ms235.5 ms261.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.41 blocks0.52 blocksno cohort
Rate limited0391,3610
Unsupported0019255
Samples8,6628,5722,0148,605

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

+16.8points

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

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

PublicNodevsMerkle

+24.0points

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

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

PublicNodevsCloudflare

+48.9points

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

The parts add to +48.9, 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