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
7d window · 2.3 days observed · generated 2026-08-27 03:22:00 UTC
| Metric | PublicNode | dRPC | Cloudflare |
|---|---|---|---|
| Rank | 1 | 3 | 9 |
| Score | 99.4 | 93.5 | 55.9 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.93% | 23.10% |
| p50 latency | 18.3 ms | 34.0 ms | 15.2 ms |
| p95 latency | 33.7 ms | 72.6 ms | 88.8 ms |
| p99 latency | 70.5 ms | 169.2 ms | 254.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | no cohort |
| Rate limited | 0 | 569 | 77 |
| Unsupported | 0 | 0 | 2,603 |
| Samples | 89,304 | 87,173 | 88,443 |
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
+5.9points
- Latency+6.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +5.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+43.5points
- Availability+29.7
- Head freshness*+9.4
- Latency+6.6
- Correctness−2.2
The parts add to +43.5, 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.