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
1h window · 60 minutes observed · generated 2026-10-08 18:55:22 UTC
| Metric | NodeReal | BNB Chain | PublicNode |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 97.3 | 95.4 | 80.0 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 99.94% |
| p50 latency | 19.3 ms | 18.3 ms | 30.3 ms |
| p95 latency | 26.2 ms | 24.8 ms | 57.2 ms |
| p99 latency | 60.7 ms | 41.1 ms | 237.8 ms |
| Correctness | 100.00% | 100.00% | 99.94% |
| Head lag | 1.68 blocks | 4.86 blocks | 4.14 blocks |
| Rate limited | 0 | 31 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,577 | 3,206 | 1,613 |
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.8points
- Head freshness+2.7
- Latency−0.8
- Availability+0.0
- Correctness+0.0
The parts add to +1.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+17.3points
- Latency+15.1
- Head freshness+2.1
- Availability+0.0
- Correctness+0.0
The parts add to +17.3, exactly — the score is a weighted sum, so it comes apart.