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

7d window · 2.6 days observed · generated 2026-08-27 11:34:32 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMEV BlockerCloudflare
Rank1579
Score99.485.277.755.1
StatusExcellentGoodGoodDegraded
Availability99.97%99.98%99.89%23.11%
p50 latency18.5 ms104.7 ms118.7 ms15.0 ms
p95 latency33.8 ms122.1 ms209.4 ms86.8 ms
p99 latency71.9 ms145.8 ms232.8 ms251.0 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.42 blocks0.40 blocksno cohort
Rate limited01,150396
Unsupported0002,995
Samples102,711101,370101,744101,749

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

+14.2points

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

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

PublicNodevsMEV Blocker

+21.7points

  • Latency+21.7
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+44.3points

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

The parts add to +44.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