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 14:56:00 UTC
| Metric | PublicNode | dRPC | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 5 | 8 |
| Score | 99.4 | 92.2 | 84.9 | 62.4 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.93% | 99.98% | 84.99% |
| p50 latency | 18.9 ms | 33.8 ms | 104.9 ms | 225.7 ms |
| p95 latency | 34.6 ms | 71.9 ms | 122.3 ms | 4391.3 ms |
| p99 latency | 73.7 ms | 169.0 ms | 146.5 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 97.48% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 644 | 1,167 | 18,434 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 108,202 | 105,607 | 106,811 | 22,528 |
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
+7.2points
- Latency+7.3
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+14.5points
- Latency+14.5
- 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.
PublicNodevs1RPC
+37.0points
- Latency+30.0
- Availability+6.0
- Correctness+0.5
- Head freshness+0.5
The parts add to +37.0, exactly — the score is a weighted sum, so it comes apart.