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 09:13:19 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleCloudflare
Rank1368
Score99.488.370.050.6
StatusExcellentGoodDegradedDegraded
Availability99.99%99.94%100.00%23.08%
p50 latency19.1 ms31.4 ms105.3 ms13.3 ms
p95 latency31.7 ms64.1 ms194.3 ms74.6 ms
p99 latency66.8 ms158.1 ms228.0 ms116.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.61 blocksno cohort
Rate limited0371,3307
Unsupported0014252
Samples8,5218,3101,9308,465

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

+11.1points

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

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

PublicNodevsMerkle

+29.4points

  • Latency+29.2
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+48.8points

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

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