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 05:45:25 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyMerkleCloudflare
Rank1269
Score99.499.477.755.8
StatusExcellentExcellentGoodDegraded
Availability99.99%100.00%100.00%23.19%
p50 latency17.5 ms18.8 ms104.7 ms12.8 ms
p95 latency32.1 ms32.3 ms193.2 ms68.1 ms
p99 latency60.3 ms65.1 ms251.0 ms160.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.48 blocks0.54 blocksno cohort
Rate limited001,4756
Unsupported0020272
Samples9,4089,3142,0899,331

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.

PublicNodevsTenderly

+0.0points

  • Latency+0.1
  • Availability0.0
  • Head freshness0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+21.7points

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

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

PublicNodevsCloudflare

+43.6points

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

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