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 23:24:32 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1369
Score99.491.478.052.3
StatusExcellentExcellentGoodDegraded
Availability99.98%99.92%100.00%23.10%
p50 latency18.5 ms34.1 ms107.0 ms16.1 ms
p95 latency34.8 ms68.4 ms195.7 ms93.9 ms
p99 latency73.0 ms167.6 ms240.0 ms247.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.46 blocksno cohort
Rate limited01216,09139
Unsupported00801,120
Samples38,22337,3088,77537,851

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.0points

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

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

PublicNodevsMerkle

+21.4points

  • Latency+21.4
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+47.1points

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

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