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

24h window · 24 hours observed · generated 2026-08-27 17:14:55 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast APIMEV BlockerCloudflare
Rank2579
Score98.283.976.953.5
StatusExcellentGoodGoodDegraded
Availability99.97%99.99%99.93%23.15%
p50 latency20.3 ms106.1 ms121.1 ms15.0 ms
p95 latency39.7 ms122.6 ms212.4 ms86.2 ms
p99 latency95.6 ms149.8 ms235.6 ms238.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.42 blocks0.40 blocksno cohort
Rate limited0323336
Unsupported0001,108
Samples37,98937,50337,59437,689

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

  • Latency+14.4
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMEV Blocker

+21.4points

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

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

PublicNodevsCloudflare

+44.7points

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

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