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
24h window · 24 hours observed · generated 2026-08-27 05:52:53 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 84.0 | 58.2 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 74.93% |
| p50 latency | 18.2 ms | 104.8 ms | 2024.4 ms |
| p95 latency | 35.1 ms | 121.5 ms | 6590.4 ms |
| p99 latency | 73.5 ms | 143.6 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 96.63% |
| Head lag | 0.48 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 0 | 320 | 6,632 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,991 | 38,456 | 7,959 |
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.4points
- Latency+15.5
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+41.2points
- Latency+30.0
- Availability+10.0
- Correctness+0.7
- Head freshness+0.5
The parts add to +41.2, exactly — the score is a weighted sum, so it comes apart.