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 08:06:11 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMerkleCloudflare
Rank1568
Score99.477.970.051.1
StatusExcellentGoodDegradedDegraded
Availability99.99%99.99%100.00%23.15%
p50 latency18.1 ms104.1 ms104.5 ms13.0 ms
p95 latency29.4 ms118.6 ms192.8 ms70.3 ms
p99 latency57.3 ms145.2 ms268.8 ms122.2 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.41 blocks0.60 blocksno cohort
Rate limited0901,2950
Unsupported0013247
Samples8,3308,2501,8468,267

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

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

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

PublicNodevsMerkle

+29.4points

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

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

PublicNodevsCloudflare

+48.3points

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

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