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 01:10:59 UTC
| Metric | PublicNode | NodeReal | 1RPC |
|---|---|---|---|
| Rank | 2 | 4 | 8 |
| Score | 98.8 | 86.2 | 61.5 |
| Status | Excellent | Good | Degraded |
| Availability | 99.94% | 100.00% | 83.23% |
| p50 latency | 17.0 ms | 87.2 ms | 1791.4 ms |
| p95 latency | 34.6 ms | 98.2 ms | 6174.8 ms |
| p99 latency | 68.7 ms | 124.0 ms | 8261.1 ms |
| Correctness | 100.00% | 100.00% | 96.69% |
| Head lag | 0.51 blocks | 0.33 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 295 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,627 | 1,595 | 642 |
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
+12.6points
- Latency+12.8
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+37.3points
- Latency+29.4
- Availability+6.7
- Correctness+0.7
- Head freshness+0.5
The parts add to +37.3, exactly — the score is a weighted sum, so it comes apart.