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
6h window · 6.0 hours observed · generated 2026-08-27 02:23:58 UTC
| Metric | PublicNode | NodeReal | Blast API |
|---|---|---|---|
| Rank | 2 | 4 | 5 |
| Score | 98.8 | 86.2 | 83.9 |
| Status | Excellent | Good | Good |
| Availability | 99.99% | 99.99% | 99.99% |
| p50 latency | 17.2 ms | 86.8 ms | 104.0 ms |
| p95 latency | 35.3 ms | 99.1 ms | 118.2 ms |
| p99 latency | 92.9 ms | 117.6 ms | 139.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.33 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 52 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,823 | 8,602 | 8,683 |
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
- Correctness+0.0
- Availability+0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+14.9points
- Latency+15.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +14.9, exactly — the score is a weighted sum, so it comes apart.