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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
30d window · 3.9 days observed · generated 2026-08-28 18:43:15 UTC
| Metric | dRPC | 1RPC | Cloudflare |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 90.9 | 61.7 | 53.6 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.95% | 83.16% | 23.12% |
| p50 latency | 33.8 ms | 265.3 ms | 14.7 ms |
| p95 latency | 73.1 ms | 4975.4 ms | 87.8 ms |
| p99 latency | 175.2 ms | 8455.9 ms | 248.2 ms |
| Correctness | 99.99% | 97.38% | 100.00% |
| Head lag | 0.36 blocks | 0.91 blocks | no cohort |
| Rate limited | 760 | 26,160 | 117 |
| Unsupported | 0 | 0 | 4,483 |
| Samples | 149,896 | 31,737 | 152,257 |
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
+29.2points
- Latency+21.3
- Availability+6.7
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.2, exactly — the score is a weighted sum, so it comes apart.
dRPCvsCloudflare
+37.3points
- Availability+29.7
- Head freshness*+9.6
- 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.