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

30d window · 2.9 days observed · generated 2026-08-27 17:52:13 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeReal1RPCCloudflare
Rank2489
Score96.787.662.454.3
StatusExcellentGoodDegradedDegraded
Availability99.96%99.83%84.99%23.11%
p50 latency19.8 ms87.4 ms225.7 ms15.3 ms
p95 latency50.4 ms100.0 ms4391.3 ms89.0 ms
p99 latency741.8 ms126.0 ms7602.5 ms252.1 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.50 blocks0.35 blocks0.91 blocksno cohort
Rate limited0019,25696
Unsupported0003,297
Samples112,137110,24423,466111,954

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.

TenderlyvsNodeReal

+9.1points

  • Latency+9.3
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

Tenderlyvs1RPC

+34.3points

  • Latency+27.3
  • Availability+6.0
  • Correctness+0.5
  • Head freshness+0.5

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

TenderlyvsCloudflare

+42.4points

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

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