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 02:29:23 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV BlockerCloudflare
Rank2379
Score98.890.276.855.3
StatusExcellentExcellentGoodDegraded
Availability99.99%99.87%99.95%23.18%
p50 latency17.2 ms33.5 ms118.0 ms12.8 ms
p95 latency35.3 ms71.1 ms209.4 ms72.3 ms
p99 latency91.8 ms175.9 ms230.2 ms260.9 ms
Correctness100.00%99.98%100.00%100.00%
Head lag0.49 blocks0.38 blocks0.40 blocksno cohort
Rate limited03326
Unsupported000258
Samples8,9738,7508,8818,898

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.

PublicNodevsdRPC

+8.6points

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

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

PublicNodevsMEV Blocker

+22.0points

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

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

PublicNodevsCloudflare

+43.5points

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

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