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.2 days observed · generated 2026-08-27 02:28:38 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV BlockerCloudflare
Rank1379
Score99.493.678.156.0
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.88%23.10%
p50 latency18.3 ms34.0 ms118.5 ms15.3 ms
p95 latency33.7 ms72.6 ms209.4 ms89.1 ms
p99 latency70.4 ms169.2 ms233.2 ms254.5 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.40 blocksno cohort
Rate limited0565277
Unsupported0002,562
Samples87,85885,75287,04487,006

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

+5.8points

  • Latency+5.9
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.2points

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

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

PublicNodevsCloudflare

+43.4points

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

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