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
1h window · 60 minutes observed · generated 2026-08-27 13:19:55 UTC
| Metric | PublicNode | dRPC | Blast API |
|---|---|---|---|
| Rank | 2 | 3 | 5 |
| Score | 95.5 | 90.5 | 78.3 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.94% | 100.00% |
| p50 latency | 25.3 ms | 33.6 ms | 108.5 ms |
| p95 latency | 47.0 ms | 62.8 ms | 125.3 ms |
| p99 latency | 105.9 ms | 169.8 ms | 149.1 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.33 blocks | 0.38 blocks |
| Rate limited | 0 | 2 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,627 | 1,587 | 1,614 |
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
+4.9points
- Latency+5.1
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +4.9, 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.