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-26 22:23:22 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank2367
Score98.486.270.769.5
StatusExcellentGoodDegradedDegraded
Availability99.92%99.86%100.00%99.94%
p50 latency18.5 ms35.6 ms108.2 ms123.3 ms
p95 latency38.8 ms78.6 ms192.3 ms213.8 ms
p99 latency88.9 ms192.5 ms234.1 ms238.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.39 blocks0.42 blocks0.41 blocks
Rate limited0391,3490
Unsupported00140
Samples8,8078,5731,9458,726

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

+12.2points

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

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

PublicNodevsMerkle

+27.7points

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

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

PublicNodevsMEV Blocker

+28.9points

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

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

Latency over time