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:27:31 UTC
| Metric | NodeReal | BNB Chain | PublicNode |
|---|---|---|---|
| Rank | 1 | 2 | 3 |
| Score | 97.6 | 95.8 | 80.9 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 99.94% |
| p50 latency | 18.2 ms | 17.8 ms | 29.9 ms |
| p95 latency | 25.2 ms | 24.4 ms | 54.6 ms |
| p99 latency | 67.4 ms | 41.1 ms | 223.2 ms |
| Correctness | 100.00% | 100.00% | 99.94% |
| Head lag | 1.62 blocks | 4.40 blocks | 3.81 blocks |
| Rate limited | 0 | 29 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,583 | 3,225 | 1,617 |
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.9points
- Head freshness+2.4
- Latency−0.5
- Availability+0.0
- Correctness+0.0
The parts add to +1.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsPublicNode
+16.7points
- Latency+14.7
- Head freshness+2.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.7, exactly — the score is a weighted sum, so it comes apart.