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.2 days observed · generated 2026-08-27 00:57:47 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 86.1 | 62.6 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.98% | 85.50% |
| p50 latency | 18.3 ms | 104.6 ms | 225.7 ms |
| p95 latency | 33.7 ms | 122.3 ms | 4391.3 ms |
| p99 latency | 70.5 ms | 144.4 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 97.48% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 967 | 14,528 |
| Unsupported | 0 | 0 | 0 |
| Samples | 85,376 | 84,184 | 18,051 |
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
+13.3points
- Latency+13.4
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+36.8points
- Latency+30.0
- Availability+5.8
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.8, exactly — the score is a weighted sum, so it comes apart.