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
24h window · 24 hours observed · generated 2026-08-27 13:53:57 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 98.8 | 90.5 | 83.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.92% | 99.99% |
| p50 latency | 19.5 ms | 34.1 ms | 105.8 ms |
| p95 latency | 37.4 ms | 72.1 ms | 122.5 ms |
| p99 latency | 87.2 ms | 171.7 ms | 149.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.41 blocks |
| Rate limited | 0 | 158 | 331 |
| Unsupported | 0 | 0 | 0 |
| Samples | 39,039 | 38,088 | 38,479 |
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
+8.2points
- Latency+8.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.