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
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-27 15:09:37 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 90.7 | 57.8 | 53.4 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.93% | 73.97% | 23.15% |
| p50 latency | 33.9 ms | 2024.4 ms | 14.9 ms |
| p95 latency | 71.6 ms | 6590.4 ms | 86.2 ms |
| p99 latency | 173.3 ms | 9196.2 ms | 208.5 ms |
| Correctness | 99.99% | 96.63% | 100.00% |
| Head lag | 0.37 blocks | 0.95 blocks | no cohort |
| Rate limited | 144 | 6,436 | 55 |
| Unsupported | 0 | 0 | 1,104 |
| Samples | 36,902 | 7,736 | 37,484 |
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.
dRPCvs1RPC
+32.9points
- Latency+21.2
- Availability+10.4
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.3points
- Availability+29.7
- Head freshness*+9.5
- Correctness−2.2
- Latency+0.3
The parts add to +37.3, 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.