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:38:49 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV BlockerCloudflare
Rank2679
Score99.277.876.955.8
StatusExcellentGoodGoodDegraded
Availability99.99%100.00%99.93%23.19%
p50 latency17.4 ms104.4 ms118.0 ms12.7 ms
p95 latency33.0 ms193.0 ms208.2 ms68.6 ms
p99 latency74.7 ms229.0 ms228.3 ms160.7 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.44 blocks0.39 blocksno cohort
Rate limited01,41426
Unsupported0200267
Samples9,2232,0069,1209,158

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

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

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

PublicNodevsMEV Blocker

+22.3points

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

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

PublicNodevsCloudflare

+43.5points

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

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