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 17:53:49 UTC

Selected providers compared across every measured metric
MetricdRPCNodeRealMEV BlockerCloudflare
Rank3478
Score89.682.969.545.8
StatusGoodGoodDegradedPoor
Availability99.96%100.00%99.89%23.08%
p50 latency34.6 ms87.5 ms125.1 ms17.6 ms
p95 latency68.4 ms99.5 ms217.5 ms107.1 ms
p99 latency180.3 ms127.3 ms242.2 ms265.2 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.36 blocks0.33 blocks0.40 blocksno cohort
Rate limited23000
Unsupported000285
Samples9,3979,3969,5239,561

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

+6.7points

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

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

dRPCvsMEV Blocker

+20.1points

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

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

dRPCvsCloudflare

+43.8points

  • Availability+29.7
  • Head freshness*+9.6
  • Latency+6.7
  • Correctness2.2

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