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 01:50:44 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMerkleCloudflare
Rank3469
Score89.886.177.654.1
StatusGoodGoodGoodDegraded
Availability99.86%99.99%100.00%23.21%
p50 latency34.1 ms87.0 ms105.9 ms13.6 ms
p95 latency73.6 ms99.3 ms193.5 ms78.8 ms
p99 latency179.6 ms121.6 ms220.4 ms266.5 ms
Correctness99.98%99.99%100.00%100.00%
Head lag0.39 blocks0.33 blocks0.51 blocksno cohort
Rate limited3301,47517
Unsupported0017275
Samples9,3109,3072,1119,467

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

dRPCvsNodeReal

+3.6points

  • Latency+3.7
  • Head freshness0.1
  • Availability0.1
  • Correctness0.0

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

dRPCvsMerkle

+12.2points

  • Latency+12.1
  • Head freshness+0.1
  • Availability0.1
  • Correctness0.0

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

dRPCvsCloudflare

+35.6points

  • Availability+29.6
  • Head freshness*+9.5
  • Correctness2.2
  • Latency1.3

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