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
- NodeReal
- BNB Chain
- PublicNode
- Blast API
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-10-08 19:23:33 UTC
| Metric | NodeReal | BNB Chain | PublicNode | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 5 |
| Score | 97.3 | 95.5 | 86.2 | 29.2 |
| Status | Excellent | Excellent | Good | Poor |
| Availability | 99.74% | 99.71% | 99.96% | 12.66% |
| p50 latency | 18.8 ms | 18.3 ms | 30.5 ms | 1438.6 ms |
| p95 latency | 26.7 ms | 25.2 ms | 56.9 ms | 7334.3 ms |
| p99 latency | 68.9 ms | 43.4 ms | 218.7 ms | 8983.2 ms |
| Correctness | 100.00% | 99.99% | 99.98% | 100.00% |
| Head lag | 1.77 blocks | 4.60 blocks | 3.95 blocks | 7.01 blocks |
| Rate limited | 0 | 169 | 0 | 1,114 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,612 | 17,572 | 8,807 | 3,425 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsBNB Chain
+1.8points
- Head freshness+2.4
- Latency−0.6
- Availability+0.0
- Correctness+0.0
The parts add to +1.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+11.2points
- Latency+9.3
- Head freshness+1.9
- Availability−0.1
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+68.1points
- Availability+34.8
- Latency+29.4
- Head freshness+3.8
- Correctness+0.0
The parts add to +68.1, exactly — the score is a weighted sum, so it comes apart.