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-28 00:18:04 UTC
| Metric | PublicNode | NodeReal | 1RPC |
|---|---|---|---|
| Rank | 1 | 4 | 8 |
| Score | 99.4 | 85.9 | 57.5 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 72.46% |
| p50 latency | 17.6 ms | 87.3 ms | 2478.9 ms |
| p95 latency | 29.2 ms | 98.8 ms | 8408.8 ms |
| p99 latency | 55.0 ms | 109.9 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 98.37% |
| Head lag | 0.47 blocks | 0.37 blocks | 1.02 blocks |
| Rate limited | 0 | 0 | 197 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,610 | 1,567 | 396 |
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.
PublicNodevsNodeReal
+13.6points
- Latency+13.7
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+42.0points
- Latency+30.0
- Availability+11.0
- Head freshness+0.6
- Correctness+0.3
The parts add to +42.0, exactly — the score is a weighted sum, so it comes apart.