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 10:35:38 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealMEV Blocker
Rank2347
Score98.987.780.869.5
StatusExcellentGoodGoodDegraded
Availability99.98%99.94%100.00%99.93%
p50 latency20.2 ms32.1 ms88.0 ms120.5 ms
p95 latency35.9 ms70.0 ms105.3 ms209.5 ms
p99 latency88.8 ms163.0 ms142.5 ms227.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.35 blocks0.35 blocks0.41 blocks
Rate limited04301
Unsupported0000
Samples9,1218,9128,9199,044

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.2points

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

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

PublicNodevsNodeReal

+18.0points

  • Latency+18.2
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+29.4points

  • Latency+29.5
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

Latency over time