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 09:56:05 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 99.3 | 90.6 | 83.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.91% | 99.99% |
| p50 latency | 18.7 ms | 34.2 ms | 105.4 ms |
| p95 latency | 35.7 ms | 71.6 ms | 122.5 ms |
| p99 latency | 76.8 ms | 176.5 ms | 146.7 ms |
| Correctness | 100.00% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.42 blocks |
| Rate limited | 0 | 157 | 365 |
| Unsupported | 0 | 0 | 0 |
| Samples | 39,087 | 38,139 | 38,546 |
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.7points
- Latency+8.8
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+15.5points
- Latency+15.6
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.