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 03:15:19 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeReal1RPC
Rank2348
Score99.190.686.458.7
StatusExcellentExcellentGoodDegraded
Availability99.99%99.94%99.99%76.33%
p50 latency17.2 ms33.2 ms86.7 ms2024.4 ms
p95 latency34.2 ms69.7 ms98.8 ms6590.4 ms
p99 latency84.8 ms167.2 ms117.6 ms9196.2 ms
Correctness100.00%99.99%99.99%96.63%
Head lag0.48 blocks0.38 blocks0.33 blocks0.95 blocks
Rate limited02701,438
Unsupported0000
Samples8,5798,3818,3882,008

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

+8.6points

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

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

PublicNodevsNodeReal

+12.7points

  • Latency+12.9
  • Head freshness0.2
  • Correctness+0.0
  • Availability+0.0

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

PublicNodevs1RPC

+40.4points

  • Latency+29.7
  • Availability+9.5
  • Correctness+0.7
  • Head freshness+0.5

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

Latency over time