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 14:18:33 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV BlockerCloudflare
Rank2479
Score98.686.476.853.3
StatusExcellentGoodGoodDegraded
Availability99.97%100.00%99.92%23.15%
p50 latency19.5 ms87.3 ms120.7 ms15.0 ms
p95 latency37.8 ms100.1 ms211.6 ms86.6 ms
p99 latency88.3 ms129.6 ms233.7 ms218.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.40 blocksno cohort
Rate limited00355
Unsupported0001,110
Samples38,08537,13737,69237,721

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

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

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

PublicNodevsMEV Blocker

+21.8points

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

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

PublicNodevsCloudflare

+45.4points

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

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