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

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleCloudflare
Rank2568
Score95.878.670.448.3
StatusExcellentGoodDegradedPoor
Availability99.98%99.99%100.00%23.14%
p50 latency24.4 ms108.0 ms108.5 ms16.2 ms
p95 latency47.9 ms125.5 ms197.2 ms94.5 ms
p99 latency122.3 ms153.3 ms231.3 ms134.5 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.50 blocks0.41 blocks0.48 blocksno cohort
Rate limited0581,27612
Unsupported0014234
Samples8,1758,1021,9018,105

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

+17.2points

  • Latency+17.3
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMerkle

+25.4points

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

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

PublicNodevsCloudflare

+47.5points

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

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