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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 11:19:04 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 84.4 | 77.9 | 49.5 |
| Status | Good | Good | Poor |
| Availability | 100.00% | 100.00% | 23.24% |
| p50 latency | 33.4 ms | 105.5 ms | 13.4 ms |
| p95 latency | 82.6 ms | 121.5 ms | 80.6 ms |
| p99 latency | 163.7 ms | 133.7 ms | 107.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.43 blocks | no cohort |
| Rate limited | 2 | 52 | 0 |
| Unsupported | 0 | 0 | 48 |
| Samples | 1,556 | 1,588 | 1,585 |
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
+6.5points
- Latency+6.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+34.9points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−2.1
The parts add to +34.9, 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.