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:14:37 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealMerkle
Rank1346
Score99.488.380.170.0
StatusExcellentGoodGoodDegraded
Availability99.99%99.94%100.00%100.00%
p50 latency19.1 ms31.4 ms87.7 ms105.3 ms
p95 latency31.6 ms64.0 ms106.1 ms194.3 ms
p99 latency66.6 ms157.9 ms142.5 ms228.0 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.36 blocks0.61 blocks
Rate limited03701,332
Unsupported00014
Samples8,5558,3478,3631,935

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.2
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsNodeReal

+19.3points

  • Latency+19.4
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

Latency over time