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 14:38:16 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCNodeRealCloudflare
Rank1349
Score99.490.586.453.2
StatusExcellentExcellentGoodDegraded
Availability99.98%99.92%100.00%23.15%
p50 latency19.2 ms34.0 ms87.3 ms15.0 ms
p95 latency34.1 ms72.2 ms100.1 ms86.9 ms
p99 latency77.2 ms173.2 ms129.6 ms218.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.34 blocksno cohort
Rate limited0150055
Unsupported0001,126
Samples38,24637,66837,66038,251

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.

TenderlyvsdRPC

+8.9points

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

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

TenderlyvsNodeReal

+13.0points

  • Latency+13.1
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+46.2points

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

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