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
6h window · 6.0 hours observed · generated 2026-08-28 00:14:15 UTC
| Metric | dRPC | Cloudflare | 1RPC |
|---|---|---|---|
| Rank | 3 | 8 | 9 |
| Score | 91.9 | 53.8 | 52.3 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.99% | 23.11% | 59.43% |
| p50 latency | 32.8 ms | 14.8 ms | 3162.4 ms |
| p95 latency | 64.2 ms | 82.3 ms | 8526.1 ms |
| p99 latency | 166.1 ms | 261.4 ms | 12423.1 ms |
| Correctness | 100.00% | 100.00% | 98.44% |
| Head lag | 0.36 blocks | no cohort | 1.00 blocks |
| Rate limited | 11 | 15 | 1,402 |
| Unsupported | 0 | 247 | 0 |
| Samples | 8,341 | 8,484 | 1,714 |
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.
dRPCvsCloudflare
+38.1points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency+1.0
The parts add to +38.1, 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
+39.6points
- Latency+22.3
- Availability+16.2
- Head freshness+0.7
- Correctness+0.3
The parts add to +39.6, exactly — the score is a weighted sum, so it comes apart.