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 06:53:58 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleCloudflare1RPC
Rank2689
Score98.970.151.70.0
StatusExcellentDegradedDegradedPoor
Availability100.00%100.00%23.16%0.00%
p50 latency18.7 ms105.0 ms12.9 ms0.0 ms
p95 latency32.2 ms192.8 ms68.8 ms0.0 ms
p99 latency64.8 ms268.8 ms141.7 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.47 blocks0.51 blocksno cohortno cohort
Rate limited01,48101,646
Unsupported0182810
Samples9,5452,1029,5561,887

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.

TenderlyvsMerkle

+28.7points

  • Latency+28.7
  • Head freshness+0.0
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+47.2points

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

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

Tenderlyvs1RPC

+98.9points

  • Availability+40.0
  • Latency*+29.5
  • Correctness*+20.0
  • Head freshness*+9.4

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