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 17:18:07 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodedRPCCloudflare
Rank1238
Score99.495.189.646.1
StatusExcellentExcellentGoodPoor
Availability99.98%100.00%99.95%23.10%
p50 latency20.3 ms25.5 ms34.5 ms17.6 ms
p95 latency33.5 ms50.0 ms68.3 ms104.9 ms
p99 latency66.4 ms112.4 ms175.6 ms261.5 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.49 blocks0.49 blocks0.36 blocksno cohort
Rate limited00210
Unsupported000255
Samples8,6018,6628,4448,605

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

+4.3points

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

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

TenderlyvsdRPC

+9.8points

  • Latency+10.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+53.3points

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

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