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 13:41:38 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APICloudflare
Rank2459
Score98.886.483.853.1
StatusExcellentGoodGoodDegraded
Availability99.97%100.00%99.99%23.14%
p50 latency19.4 ms87.3 ms105.7 ms15.1 ms
p95 latency37.3 ms100.1 ms122.5 ms87.9 ms
p99 latency86.8 ms128.7 ms149.0 ms216.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.41 blocksno cohort
Rate limited0033155
Unsupported0001,127
Samples38,70537,75138,15638,330

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.

PublicNodevsNodeReal

+12.4points

  • Latency+12.5
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsBlast API

+15.0points

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

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

PublicNodevsCloudflare

+45.7points

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

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