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 BSC
Side by side
24h window · 24 hours observed · generated 2026-10-08 18:13:09 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 85.9 | 76.5 | 28.2 |
| Status | Good | Good | Poor |
| Availability | 99.99% | 100.00% | 9.51% |
| p50 latency | 26.6 ms | 105.1 ms | 716.3 ms |
| p95 latency | 56.4 ms | 124.6 ms | 5991.9 ms |
| p99 latency | 173.8 ms | 146.7 ms | 8622.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 4.03 blocks | 3.30 blocks | 6.57 blocks |
| Rate limited | 0 | 466 | 5,116 |
| Unsupported | 0 | 0 | 1 |
| Samples | 37,941 | 37,385 | 12,784 |
5 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
+9.5points
- Latency+10.0
- Head freshness−0.6
- Availability−0.0
- Correctness−0.0
The parts add to +9.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+57.7points
- Availability+36.2
- Latency+19.9
- Head freshness+1.6
- Correctness−0.0
The parts add to +57.7, exactly — the score is a weighted sum, so it comes apart.