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:09:15 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV BlockerCloudflare
Rank1478
Score99.482.969.547.0
StatusExcellentGoodDegradedPoor
Availability99.98%100.00%99.88%23.15%
p50 latency20.2 ms87.4 ms124.8 ms17.2 ms
p95 latency33.4 ms99.5 ms217.1 ms101.1 ms
p99 latency64.5 ms133.5 ms243.1 ms250.9 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.33 blocks0.40 blocksno cohort
Rate limited0000
Unsupported000247
Samples8,3638,1998,3428,358

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

+16.5points

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

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

TenderlyvsMEV Blocker

+29.9points

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

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

TenderlyvsCloudflare

+52.4points

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

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