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

1h window · 60 minutes observed · generated 2026-08-27 13:30:17 UTC

Selected providers compared across every measured metric
MetricdRPCBlast APICloudflare1RPC
Rank3589
Score91.078.245.00.0
StatusExcellentGoodPoorPoor
Availability99.94%100.00%22.84%0.00%
p50 latency34.1 ms108.5 ms17.3 ms0.0 ms
p95 latency61.7 ms126.0 ms108.3 ms0.0 ms
p99 latency153.5 ms153.1 ms250.1 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.33 blocks0.41 blocksno cohortno cohort
Rate limited200275
Unsupported00480
Samples1,5701,5881,605319

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.

dRPCvsBlast API

+12.8points

  • Latency+12.8
  • Head freshness+0.1
  • Availability0.0
  • Correctness+0.0

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

dRPCvsCloudflare

+46.0points

  • Availability+29.8
  • Head freshness*+9.6
  • Latency+8.8
  • Correctness2.2

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

dRPCvs1RPC

+91.0points

  • Availability+40.0
  • Latency*+21.4
  • Correctness*+20.0
  • Head freshness*+9.6

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