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-28 02:10:02 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 83.5 | 60.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.99% | 79.94% |
| p50 latency | 19.1 ms | 104.1 ms | 1326.0 ms |
| p95 latency | 31.1 ms | 119.8 ms | 7406.7 ms |
| p99 latency | 63.8 ms | 147.7 ms | 9776.0 ms |
| Correctness | 99.98% | 99.99% | 96.96% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.94 blocks |
| Rate limited | 0 | 35 | 1,407 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,443 | 8,372 | 1,964 |
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.
PublicNodevsBlast API
+15.9points
- Latency+16.0
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +15.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.