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:25:04 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodedRPCCloudflare
Rank1238
Score99.495.686.647.7
StatusExcellentExcellentGoodPoor
Availability100.00%99.94%99.94%23.37%
p50 latency20.9 ms24.7 ms34.0 ms16.9 ms
p95 latency34.3 ms48.5 ms80.5 ms97.9 ms
p99 latency66.4 ms101.1 ms193.6 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.48 blocks0.38 blocksno cohort
Rate limited00100
Unsupported00045
Samples1,6011,6101,5731,593

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.8points

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

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

TenderlyvsdRPC

+12.8points

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

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

TenderlyvsCloudflare

+51.7points

  • Availability+29.6
  • Latency+14.9
  • Head freshness*+9.4
  • Correctness2.2

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