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-26 20:09:49 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV BlockerCloudflare
Rank1379
Score99.491.577.252.4
StatusExcellentExcellentGoodDegraded
Availability99.97%99.94%99.86%23.09%
p50 latency18.8 ms34.0 ms118.8 ms15.9 ms
p95 latency33.8 ms67.5 ms210.3 ms93.6 ms
p99 latency71.2 ms166.4 ms232.7 ms246.3 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.37 blocks0.39 blocksno cohort
Rate limited0109028
Unsupported0001,110
Samples37,82136,93737,46337,446

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

+7.9points

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

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

PublicNodevsMEV Blocker

+22.2points

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

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

PublicNodevsCloudflare

+47.0points

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

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