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:50:30 UTC
| Metric | NodeReal | PublicNode | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 5 |
| Score | 97.4 | 86.3 | 76.3 | 29.2 |
| Status | Excellent | Good | Good | Poor |
| Availability | 99.76% | 99.97% | 99.98% | 12.66% |
| p50 latency | 18.8 ms | 30.4 ms | 110.8 ms | 1438.6 ms |
| p95 latency | 26.5 ms | 56.5 ms | 132.2 ms | 7334.3 ms |
| p99 latency | 67.8 ms | 220.2 ms | 165.2 ms | 8983.2 ms |
| Correctness | 100.00% | 99.98% | 99.99% | 100.00% |
| Head lag | 1.75 blocks | 3.94 blocks | 3.33 blocks | 7.01 blocks |
| Rate limited | 0 | 0 | 127 | 1,238 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 9,327 | 9,541 | 9,327 | 3,568 |
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
+11.1points
- Latency+9.3
- Head freshness+1.9
- Availability−0.1
- Correctness+0.0
The parts add to +11.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.1points
- Latency+19.8
- Head freshness+1.4
- Availability−0.1
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+68.2points
- Availability+34.8
- Latency+29.5
- Head freshness+3.9
- Correctness+0.0
The parts add to +68.2, exactly — the score is a weighted sum, so it comes apart.