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-28 13:37:48 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 2 | 3 | 9 |
| Score | 98.2 | 89.6 | 53.0 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 23.13% |
| p50 latency | 21.7 ms | 33.2 ms | 13.9 ms |
| p95 latency | 38.1 ms | 76.1 ms | 86.5 ms |
| p99 latency | 84.0 ms | 195.4 ms | 170.9 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 63 | 21 |
| Unsupported | 0 | 0 | 1,127 |
| Samples | 38,622 | 37,673 | 38,302 |
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.6points
- Latency+8.7
- Head freshness−0.1
- Correctness−0.0
- Availability+0.0
The parts add to +8.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+45.2points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.3
- Correctness−2.2
The parts add to +45.2, 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.