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
24h window · 24 hours observed · generated 2026-08-27 00:25:42 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 91.3 | 52.4 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.92% | 23.10% |
| p50 latency | 18.4 ms | 34.1 ms | 16.2 ms |
| p95 latency | 35.0 ms | 68.6 ms | 93.5 ms |
| p99 latency | 73.5 ms | 168.9 ms | 247.5 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | no cohort |
| Rate limited | 0 | 125 | 45 |
| Unsupported | 0 | 0 | 1,121 |
| Samples | 38,249 | 37,342 | 37,887 |
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.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.0points
- Availability+29.7
- Latency+10.1
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.0, 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.