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

30d window · 2.8 days observed · generated 2026-08-27 17:01:37 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV Blocker1RPC
Rank2478
Score96.687.677.562.4
StatusExcellentGoodGoodDegraded
Availability99.96%99.83%99.89%84.99%
p50 latency19.8 ms87.4 ms119.0 ms225.7 ms
p95 latency51.1 ms100.0 ms210.1 ms4391.3 ms
p99 latency750.5 ms126.2 ms233.8 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.50 blocks0.35 blocks0.40 blocks0.91 blocks
Rate limited00319,021
Unsupported0000
Samples110,766108,895110,56323,199

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 Tenderly, the highest scorer of those selected.

TenderlyvsNodeReal

+9.0points

  • Latency+9.1
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

TenderlyvsMEV Blocker

+19.0points

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

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

Tenderlyvs1RPC

+34.2points

  • Latency+27.2
  • Availability+6.0
  • Correctness+0.5
  • Head freshness+0.5

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

Latency over time