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
6h window · 6.0 hours observed · generated 2026-10-08 18:00:09 UTC
| Metric | PublicNode | 1RPC |
|---|---|---|
| Rank | 3 | 5 |
| Score | 86.2 | 27.3 |
| Status | Good | Poor |
| Availability | 99.99% | 7.96% |
| p50 latency | 30.2 ms | 1438.6 ms |
| p95 latency | 56.9 ms | 7334.3 ms |
| p99 latency | 170.0 ms | 8983.2 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 3.97 blocks | 7.01 blocks |
| Rate limited | 0 | 789 |
| Unsupported | 0 | 0 |
| Samples | 8,160 | 4,336 |
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.8points
- Availability+36.8
- Latency+20.1
- Head freshness+1.9
- Correctness−0.0
The parts add to +58.8, exactly — the score is a weighted sum, so it comes apart.