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.

Not sure who to compare?Start from who leads, then compareThe ranked answer per chain, with the figures that produced it.

Providers on Ethereum

Side by side

6h window · 6.0 hours observed · generated 2026-08-28 18:15:42 UTC

Selected providers compared across every measured metric
MetricPublicNodeCloudflare1RPC
Rank289
Score98.047.70.0
StatusExcellentPoorPoor
Availability100.00%23.17%0.00%
p50 latency22.8 ms14.4 ms0.0 ms
p95 latency39.2 ms93.8 ms0.0 ms
p99 latency77.5 ms167.6 ms0.0 ms
Correctness100.00%100.00%not measured
Head lag0.50 blocksno cohortno cohort
Rate limited001,467
Unsupported02520
Samples8,6048,5391,683

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.

PublicNodevsCloudflare

+50.2points

  • Availability+29.7
  • Latency+13.4
  • Head freshness*+9.4
  • Correctness−2.2

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

PublicNodevs1RPC

+98.0points

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

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