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
24h window · 24 hours observed · generated 2026-10-08 20:18:10 UTC
| Metric | NodeReal | PublicNode | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 4 | 5 |
| Score | 97.3 | 86.1 | 76.4 | 28.2 |
| Status | Excellent | Good | Good | Poor |
| Availability | 99.94% | 99.98% | 99.99% | 9.52% |
| p50 latency | 18.7 ms | 26.8 ms | 105.3 ms | 716.3 ms |
| p95 latency | 27.1 ms | 55.9 ms | 125.8 ms | 5991.9 ms |
| p99 latency | 58.1 ms | 176.8 ms | 150.5 ms | 8622.8 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 100.00% |
| Head lag | 1.71 blocks | 4.03 blocks | 3.32 blocks | 6.57 blocks |
| Rate limited | 0 | 0 | 473 | 5,147 |
| Unsupported | 0 | 0 | 0 | 1 |
| Samples | 37,189 | 38,085 | 37,484 | 12,815 |
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.2points
- Latency+9.2
- Head freshness+2.0
- Availability−0.0
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+20.9points
- Latency+19.4
- Head freshness+1.5
- Availability−0.0
- Correctness+0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+69.1points
- Availability+36.2
- Latency+29.3
- Head freshness+3.7
- Correctness+0.0
The parts add to +69.1, exactly — the score is a weighted sum, so it comes apart.