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 04:12:40 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkle1RPCCloudflare
Rank2689
Score99.277.759.055.8
StatusExcellentGoodDegradedDegraded
Availability99.99%100.00%76.94%23.19%
p50 latency17.4 ms104.4 ms2024.4 ms12.7 ms
p95 latency33.2 ms193.2 ms6590.4 ms68.4 ms
p99 latency80.7 ms251.0 ms9196.2 ms227.5 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.45 blocks0.95 blocksno cohort
Rate limited01,3161,4246
Unsupported0190245
Samples8,5151,8611,9908,449

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.

PublicNodevsMerkle

+21.5points

  • Latency+21.5
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevs1RPC

+40.2points

  • Latency+29.8
  • Availability+9.2
  • Correctness+0.7
  • Head freshness+0.5

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