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.3 days observed · generated 2026-08-27 04:01:20 UTC
| Metric | PublicNode | NodeReal | Blast API |
|---|---|---|---|
| Rank | 1 | 4 | 5 |
| Score | 99.4 | 88.7 | 85.8 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.79% | 99.98% |
| p50 latency | 18.2 ms | 87.3 ms | 104.5 ms |
| p95 latency | 33.6 ms | 99.8 ms | 122.1 ms |
| p99 latency | 70.3 ms | 123.3 ms | 144.2 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 987 |
| Unsupported | 0 | 0 | 0 |
| Samples | 90,374 | 88,170 | 89,145 |
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
+10.7points
- Latency+10.8
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +10.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+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.