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
30d window · 2.8 days observed · generated 2026-08-27 16:35:47 UTC
| Metric | PublicNode | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 1 | 5 | 9 |
| Score | 99.4 | 84.9 | 54.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 23.11% |
| p50 latency | 19.0 ms | 105.0 ms | 15.2 ms |
| p95 latency | 35.0 ms | 122.5 ms | 88.4 ms |
| p99 latency | 74.7 ms | 147.2 ms | 251.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 1,193 | 96 |
| Unsupported | 0 | 0 | 3,236 |
| Samples | 110,924 | 109,498 | 109,896 |
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.
PublicNodevsBlast API
+14.5points
- Latency+14.6
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.9points
- Availability+29.7
- Head freshness*+9.4
- Latency+8.0
- Correctness−2.2
The parts add to +44.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.