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
7d window · 2.7 days observed · generated 2026-08-27 13:17:09 UTC
| Metric | PublicNode | NodeReal | Blast API |
|---|---|---|---|
| Rank | 1 | 4 | 5 |
| Score | 99.4 | 87.8 | 85.0 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.82% | 99.98% |
| p50 latency | 18.7 ms | 87.4 ms | 104.8 ms |
| p95 latency | 34.2 ms | 100.1 ms | 122.2 ms |
| p99 latency | 72.7 ms | 125.8 ms | 146.1 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.35 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 1,154 |
| Unsupported | 0 | 0 | 0 |
| Samples | 105,511 | 102,938 | 104,142 |
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
+11.6points
- Latency+11.7
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +11.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+14.4points
- Latency+14.4
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +14.4, exactly — the score is a weighted sum, so it comes apart.