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 09:11:30 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyBlast APICloudflare
Rank1258
Score99.499.078.050.5
StatusExcellentExcellentGoodDegraded
Availability99.99%99.98%99.99%23.10%
p50 latency19.0 ms18.5 ms104.8 ms13.3 ms
p95 latency31.7 ms32.8 ms120.1 ms74.7 ms
p99 latency66.0 ms105.1 ms147.2 ms116.8 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.48 blocks0.48 blocks0.41 blocksno cohort
Rate limited001117
Unsupported000251
Samples8,4658,3938,3878,413

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 PublicNode, the highest scorer of those selected.

PublicNodevsTenderly

+0.4points

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

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

PublicNodevsBlast API

+21.4points

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

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

PublicNodevsCloudflare

+48.9points

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

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