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

30d window · 42 hours observed · generated 2026-08-26 15:00:33 UTC

Selected providers compared across every measured metric
MetricBlast APIMerkleMEV BlockerCloudflare
Rank4679
Score85.578.477.655.7
StatusGoodGoodGoodDegraded
Availability99.98%99.97%99.87%23.09%
p50 latency104.4 ms106.4 ms118.0 ms15.2 ms
p95 latency122.4 ms196.9 ms208.6 ms88.2 ms
p99 latency144.6 ms245.5 ms233.1 ms256.3 ms
Correctness99.98%100.00%99.98%100.00%
Head lag0.42 blocks0.47 blocks0.40 blocksno cohort
Rate limited82311,122041
Unsupported013702,018
Samples68,28116,03268,48468,483

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

Blast APIvsMerkle

+7.1points

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

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

Blast APIvsMEV Blocker

+7.9points

  • Latency+7.9
  • Availability+0.0
  • Head freshness0.0
  • Correctness+0.0

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

Blast APIvsCloudflare

+29.8points

  • Availability+29.7
  • Head freshness*+9.5
  • Latency7.2
  • Correctness2.2

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