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

24h window · 24 hours observed · generated 2026-08-26 21:13:23 UTC

Selected providers compared across every measured metric
MetricNodeRealBlast APIMEV Blocker1RPC
Rank4578
Score86.684.277.264.4
StatusGoodGoodGoodDegraded
Availability100.00%99.98%99.87%89.75%
p50 latency87.4 ms104.1 ms119.0 ms259.6 ms
p95 latency100.1 ms120.6 ms210.5 ms2579.7 ms
p99 latency124.8 ms138.3 ms232.6 ms4625.5 ms
Correctness100.00%99.98%99.99%98.18%
Head lag0.35 blocks0.42 blocks0.39 blocks0.94 blocks
Rate limited036306,448
Unsupported0000
Samples36,99237,45637,5427,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 NodeReal, the highest scorer of those selected.

NodeRealvsBlast API

+2.4points

  • Latency+2.3
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

NodeRealvsMEV Blocker

+9.4points

  • Latency+9.3
  • Head freshness+0.1
  • Availability+0.1
  • Correctness+0.0

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

NodeRealvs1RPC

+22.2points

  • Latency+17.0
  • Availability+4.1
  • Head freshness+0.7
  • Correctness+0.4

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

Latency over time