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
MetricTenderlyBlast APIMerkleCloudflare
Rank2568
Score98.978.370.151.7
StatusExcellentGoodDegradedDegraded
Availability100.00%99.98%100.00%23.16%
p50 latency18.7 ms103.3 ms105.0 ms12.9 ms
p95 latency32.2 ms116.7 ms192.8 ms68.8 ms
p99 latency64.8 ms144.2 ms268.8 ms141.7 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.47 blocks0.42 blocks0.51 blocksno cohort
Rate limited0791,4810
Unsupported0018281
Samples9,5459,5482,1029,556

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.

TenderlyvsBlast API

+20.6points

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

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

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.

Latency over time