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-27 08:27:58 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMEV BlockerCloudflare
Rank1279
Score99.499.476.952.5
StatusExcellentExcellentGoodDegraded
Availability99.97%99.98%99.92%23.13%
p50 latency19.4 ms18.4 ms120.0 ms15.7 ms
p95 latency35.3 ms35.4 ms210.3 ms91.0 ms
p99 latency126.1 ms74.1 ms232.5 ms241.4 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.48 blocks0.40 blocksno cohort
Rate limited00343
Unsupported0001,122
Samples37,97238,31537,93637,948

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.

TenderlyvsPublicNode

+0.0points

  • Latency+0.0
  • Head freshness0.0
  • Correctness0.0
  • Availability0.0

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

TenderlyvsMEV Blocker

+22.5points

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

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

TenderlyvsCloudflare

+46.9points

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

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