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
6h window · 6.0 hours observed · generated 2026-10-08 18:00:09 UTC
| Metric | NodeReal | BNB Chain | PublicNode |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 97.1 | 95.6 | 86.2 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.99% | 99.99% |
| p50 latency | 18.7 ms | 18.3 ms | 30.2 ms |
| p95 latency | 27.4 ms | 25.3 ms | 56.9 ms |
| p99 latency | 71.5 ms | 43.1 ms | 170.0 ms |
| Correctness | 100.00% | 99.99% | 99.99% |
| Head lag | 1.85 blocks | 4.60 blocks | 3.97 blocks |
| Rate limited | 0 | 157 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 7,993 | 16,332 | 8,160 |
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.5points
- Head freshness+2.3
- Latency−0.8
- Availability+0.0
- Correctness+0.0
The parts add to +1.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+11.0points
- Latency+9.1
- Head freshness+1.8
- Availability+0.0
- Correctness+0.0
The parts add to +11.0, exactly — the score is a weighted sum, so it comes apart.