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
30d window · 2.1 days observed · generated 2026-08-27 00:06:23 UTC
| Metric | PublicNode | 1RPC |
|---|---|---|
| Rank | 1 | 8 |
| Score | 99.4 | 63.3 |
| Status | Excellent | Degraded |
| Availability | 99.97% | 87.03% |
| p50 latency | 18.3 ms | 191.7 ms |
| p95 latency | 33.7 ms | 3436.8 ms |
| p99 latency | 70.5 ms | 6731.9 ms |
| Correctness | 99.99% | 97.66% |
| Head lag | 0.49 blocks | 0.89 blocks |
| Rate limited | 0 | 14,294 |
| Unsupported | 0 | 0 |
| Samples | 83,976 | 17,455 |
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.
PublicNodevs1RPC
+36.1points
- Latency+30.0
- Availability+5.2
- Head freshness+0.5
- Correctness+0.5
The parts add to +36.1, exactly — the score is a weighted sum, so it comes apart.