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 20:51:22 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 94.5 | 89.0 | 78.4 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.98% | 99.92% |
| p50 latency | 25.3 ms | 35.0 ms | 108.8 ms |
| p95 latency | 52.2 ms | 71.0 ms | 127.3 ms |
| p99 latency | 113.5 ms | 191.2 ms | 154.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.47 blocks | 0.35 blocks | 0.41 blocks |
| Rate limited | 0 | 24 | 67 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,573 | 9,336 | 9,473 |
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.4points
- Latency+5.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +5.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+16.1points
- Latency+16.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.1, exactly — the score is a weighted sum, so it comes apart.