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
1h window · 60 minutes observed · generated 2026-08-28 00:01:46 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 91.4 | 55.3 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 23.08% |
| p50 latency | 17.7 ms | 31.7 ms | 12.7 ms |
| p95 latency | 29.3 ms | 60.6 ms | 67.9 ms |
| p99 latency | 52.3 ms | 148.1 ms | 130.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 2 | 0 |
| Unsupported | 0 | 0 | 49 |
| Samples | 1,631 | 1,577 | 1,611 |
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
+8.0points
- Latency+8.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.2
- Correctness−2.2
The parts add to +44.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.