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 19:42:58 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMEV BlockerCloudflare
Rank1279
Score99.497.876.853.6
StatusExcellentExcellentGoodDegraded
Availability99.98%99.99%99.93%23.17%
p50 latency19.2 ms21.0 ms121.2 ms15.1 ms
p95 latency33.1 ms41.1 ms212.7 ms86.1 ms
p99 latency75.1 ms101.7 ms235.0 ms249.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.49 blocks0.40 blocksno cohort
Rate limited00336
Unsupported0001,130
Samples38,38038,75538,33838,444

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

+1.6points

  • Latency+1.6
  • Availability0.0
  • Head freshness+0.0
  • Correctness0.0

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

TenderlyvsMEV Blocker

+22.6points

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

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

TenderlyvsCloudflare

+45.8points

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

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