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 16:27:21 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV BlockerCloudflare
Rank2478
Score95.182.869.546.5
StatusExcellentGoodDegradedPoor
Availability99.99%100.00%99.89%23.15%
p50 latency25.3 ms87.4 ms124.8 ms17.2 ms
p95 latency49.6 ms99.5 ms217.2 ms102.9 ms
p99 latency112.7 ms132.4 ms243.1 ms250.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.33 blocks0.40 blocksno cohort
Rate limited0000
Unsupported000262
Samples8,9198,6838,8258,851

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.

PublicNodevsNodeReal

+12.3points

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

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

PublicNodevsMEV Blocker

+25.6points

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

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

PublicNodevsCloudflare

+48.5points

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

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