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
Side by side
30d window · 30.0 days observed · generated 2026-10-08 18:13:41 UTC
| Metric | NodeReal | BNB Chain | PublicNode |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 96.8 | 95.7 | 91.0 |
| Status | Excellent | Excellent | Excellent |
| Availability | 99.96% | 99.97% | 99.92% |
| p50 latency | 19.3 ms | 18.4 ms | 21.9 ms |
| p95 latency | 33.2 ms | 29.5 ms | 43.1 ms |
| p99 latency | 72.3 ms | 50.1 ms | 112.6 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 1.70 blocks | 4.54 blocks | 4.19 blocks |
| Rate limited | 0 | 22,787 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,138,335 | 2,332,168 | 1,165,906 |
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.1points
- Head freshness+2.4
- Latency−1.3
- Availability−0.0
- Correctness+0.0
The parts add to +1.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+5.8points
- Latency+3.6
- Head freshness+2.2
- Availability+0.0
- Correctness+0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.