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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 09:59:11 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 79.3 | 49.5 |
| Status | Excellent | Good | Poor |
| Availability | 99.98% | 99.96% | 23.10% |
| p50 latency | 19.6 ms | 31.5 ms | 12.1 ms |
| p95 latency | 31.2 ms | 111.2 ms | 78.5 ms |
| p99 latency | 58.0 ms | 250.5 ms | 133.1 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | no cohort |
| Rate limited | 0 | 23 | 0 |
| Unsupported | 0 | 0 | 283 |
| Samples | 9,773 | 9,551 | 9,698 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+20.1points
- Latency+20.2
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +20.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+49.9points
- Availability+29.7
- Latency+13.0
- Head freshness*+9.4
- Correctness−2.2
The parts add to +49.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.