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
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 14:21:54 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 95.6 | 88.3 | 78.6 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.95% | 99.99% |
| p50 latency | 24.6 ms | 33.9 ms | 108.1 ms |
| p95 latency | 48.4 ms | 73.6 ms | 125.8 ms |
| p99 latency | 120.7 ms | 173.5 ms | 153.3 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.41 blocks |
| Rate limited | 0 | 37 | 58 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,771 | 8,552 | 8,695 |
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.4points
- Latency+7.5
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+17.1points
- Latency+17.2
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.1, exactly — the score is a weighted sum, so it comes apart.