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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 12:21:56 UTC
| Metric | dRPC | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 3 | 5 | 8 |
| Score | 87.8 | 79.0 | 46.9 |
| Status | Good | Good | Poor |
| Availability | 100.00% | 99.94% | 23.11% |
| p50 latency | 34.4 ms | 107.0 ms | 13.2 ms |
| p95 latency | 71.0 ms | 121.6 ms | 98.4 ms |
| p99 latency | 179.1 ms | 134.3 ms | 136.1 ms |
| Correctness | 100.00% | 99.94% | 100.00% |
| Head lag | 0.36 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 49 |
| Samples | 1,592 | 1,613 | 1,622 |
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
+8.8points
- Latency+8.7
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+40.9points
- Availability+29.7
- Head freshness*+9.6
- Latency+3.8
- Correctness−2.2
The parts add to +40.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.