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-26 21:29:13 UTC

Selected providers compared across every measured metric
MetricdRPCMerkleMEV BlockerCloudflare
Rank3679
Score91.478.077.252.3
StatusExcellentGoodGoodDegraded
Availability99.94%100.00%99.87%23.09%
p50 latency34.1 ms106.8 ms119.1 ms16.0 ms
p95 latency68.2 ms196.1 ms210.5 ms93.9 ms
p99 latency165.8 ms241.2 ms232.9 ms247.5 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.37 blocks0.46 blocks0.39 blocksno cohort
Rate limited1146,141039
Unsupported07901,122
Samples37,4608,87437,96937,955

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.

dRPCvsMerkle

+13.4points

  • Latency+13.3
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

dRPCvsMEV Blocker

+14.2points

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

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

dRPCvsCloudflare

+39.1points

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

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