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
7d window · 7.0 days observed · generated 2026-10-08 18:12:59 UTC
| Metric | PublicNode | 1RPC |
|---|---|---|
| Rank | 3 | 5 |
| Score | 88.9 | 30.0 |
| Status | Good | Poor |
| Availability | 99.97% | 16.28% |
| p50 latency | 22.8 ms | 494.5 ms |
| p95 latency | 45.7 ms | 6063.9 ms |
| p99 latency | 142.8 ms | 9149.9 ms |
| Correctness | 99.98% | 99.63% |
| Head lag | 4.11 blocks | 8.31 blocks |
| Rate limited | 0 | 40,204 |
| Unsupported | 0 | 1 |
| Samples | 264,970 | 65,002 |
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.
PublicNodevs1RPC
+58.9points
- Availability+33.5
- Latency+22.9
- Head freshness+2.4
- Correctness+0.1
The parts add to +58.9, exactly — the score is a weighted sum, so it comes apart.