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

30d window · 3.0 days observed · generated 2026-08-27 19:43:37 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV BlockerCloudflare
Rank1479
Score99.487.577.554.2
StatusExcellentGoodGoodDegraded
Availability99.98%99.84%99.89%23.11%
p50 latency19.3 ms87.4 ms119.3 ms15.3 ms
p95 latency35.7 ms100.0 ms210.5 ms89.4 ms
p99 latency77.0 ms125.8 ms234.1 ms253.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.35 blocks0.40 blocksno cohort
Rate limited00396
Unsupported0003,386
Samples116,039113,197114,931114,960

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

+11.9points

  • Latency+12.0
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.9points

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

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

PublicNodevsCloudflare

+45.2points

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

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