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

24h window · 24 hours observed · generated 2026-08-27 01:54:55 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMEV BlockerCloudflare
Rank3479
Score91.186.677.152.3
StatusExcellentGoodGoodDegraded
Availability99.92%100.00%99.89%23.12%
p50 latency34.1 ms87.3 ms119.2 ms16.1 ms
p95 latency69.4 ms100.0 ms210.7 ms93.5 ms
p99 latency170.4 ms124.4 ms233.8 ms247.0 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.38 blocks0.34 blocks0.39 blocksno cohort
Rate limited1280245
Unsupported0001,141
Samples38,13438,10038,68138,675

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

+4.5points

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

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

dRPCvsMEV Blocker

+14.1points

  • Latency+14.0
  • Head freshness+0.0
  • Availability+0.0
  • Correctness0.0

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

dRPCvsCloudflare

+38.8points

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

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