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 20:10:40 UTC
| Metric | NodeReal | PublicNode | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 5 |
| Score | 97.5 | 86.8 | 76.2 | 37.2 |
| Status | Excellent | Good | Good | Poor |
| Availability | 99.73% | 99.95% | 99.96% | 32.74% |
| p50 latency | 18.8 ms | 30.1 ms | 110.6 ms | 1358.8 ms |
| p95 latency | 26.4 ms | 54.4 ms | 132.7 ms | 7334.3 ms |
| p99 latency | 64.2 ms | 221.1 ms | 167.6 ms | 8983.2 ms |
| Correctness | 100.00% | 99.98% | 99.99% | 100.00% |
| Head lag | 1.77 blocks | 3.95 blocks | 3.38 blocks | 7.15 blocks |
| Rate limited | 0 | 0 | 115 | 1,329 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,265 | 8,458 | 8,246 | 2,269 |
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.
NodeRealvsPublicNode
+10.7points
- Latency+8.9
- Head freshness+1.9
- Availability−0.1
- Correctness+0.0
The parts add to +10.7, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.2points
- Latency+19.9
- Head freshness+1.5
- Availability−0.1
- Correctness+0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+60.3points
- Latency+29.6
- Availability+26.8
- Head freshness+3.9
- Correctness+0.0
The parts add to +60.3, exactly — the score is a weighted sum, so it comes apart.