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

1h window · 60 minutes observed · generated 2026-08-27 12:29:48 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMEV BlockerCloudflare
Rank1278
Score99.496.069.548.6
StatusExcellentExcellentDegradedPoor
Availability100.00%99.94%99.88%23.29%
p50 latency21.0 ms24.8 ms124.5 ms17.0 ms
p95 latency34.2 ms47.0 ms217.6 ms93.7 ms
p99 latency66.8 ms101.1 ms235.7 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.50 blocks0.47 blocks0.41 blocksno cohort
Rate limited0000
Unsupported00048
Samples1,6221,6211,6071,615

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

+3.4points

  • Latency+3.4
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+29.9points

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

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

TenderlyvsCloudflare

+50.8points

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

The parts add to +50.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