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 08:32:06 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMEV BlockerCloudflare
Rank3478
Score88.180.069.551.0
StatusGoodGoodDegradedDegraded
Availability99.95%100.00%99.90%23.17%
p50 latency31.3 ms87.7 ms119.2 ms13.1 ms
p95 latency63.1 ms105.2 ms207.7 ms71.6 ms
p99 latency159.4 ms139.6 ms226.1 ms119.9 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.37 blocks0.36 blocks0.42 blocksno cohort
Rate limited32017
Unsupported000268
Samples8,8118,8328,9478,970

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

+8.1points

  • Latency+8.2
  • Availability0.0
  • Head freshness0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+18.7points

  • Latency+18.6
  • Head freshness+0.1
  • Availability+0.0
  • Correctness0.0

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

dRPCvsCloudflare

+37.2points

  • Availability+29.7
  • Head freshness*+9.5
  • Correctness2.2
  • Latency+0.2

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