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:09:20 UTC
| Metric | NodeReal | BNB Chain | PublicNode | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 5 |
| Score | 97.5 | 95.6 | 86.1 | 29.2 |
| Status | Excellent | Excellent | Good | Poor |
| Availability | 100.00% | 99.99% | 99.96% | 12.66% |
| p50 latency | 18.8 ms | 18.4 ms | 30.5 ms | 1438.6 ms |
| p95 latency | 26.6 ms | 25.2 ms | 57.0 ms | 7334.3 ms |
| p99 latency | 68.8 ms | 42.3 ms | 216.0 ms | 8983.2 ms |
| Correctness | 100.00% | 99.99% | 99.98% | 100.00% |
| Head lag | 1.79 blocks | 4.63 blocks | 3.96 blocks | 7.01 blocks |
| Rate limited | 0 | 162 | 0 | 1,045 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,236 | 16,807 | 8,413 | 3,346 |
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.9points
- Head freshness+2.4
- Latency−0.5
- Availability+0.0
- Correctness+0.0
The parts add to +1.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+11.4points
- Latency+9.5
- Head freshness+1.9
- Availability+0.0
- Correctness+0.0
The parts add to +11.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+68.2points
- Availability+34.9
- Latency+29.5
- Head freshness+3.8
- Correctness+0.0
The parts add to +68.2, exactly — the score is a weighted sum, so it comes apart.