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:10:20 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV Blocker1RPC
Rank2379
Score95.288.969.50.0
StatusExcellentGoodDegradedPoor
Availability99.99%99.94%99.88%0.00%
p50 latency25.3 ms34.4 ms124.9 ms0.0 ms
p95 latency49.5 ms70.8 ms217.1 ms0.0 ms
p99 latency110.1 ms187.6 ms243.0 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.49 blocks0.36 blocks0.40 blocksno cohort
Rate limited02001,444
Unsupported0000
Samples8,4608,2268,3631,660

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

+6.2points

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

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

PublicNodevsMEV Blocker

+25.7points

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

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

PublicNodevs1RPC

+95.2points

  • Availability+40.0
  • Latency*+25.8
  • Correctness*+20.0
  • Head freshness*+9.4

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