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:28:34 UTC
| Metric | NodeReal | BNB Chain | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 97.7 | 95.7 | 0.0 |
| Status | Excellent | Excellent | Poor |
| Availability | 100.00% | 100.00% | 0.00% |
| p50 latency | 18.3 ms | 17.9 ms | 0.0 ms |
| p95 latency | 25.2 ms | 24.5 ms | 0.0 ms |
| p99 latency | 67.4 ms | 39.8 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 1.62 blocks | 4.47 blocks | no cohort |
| Rate limited | 0 | 31 | 264 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,590 | 3,233 | 317 |
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
+2.0points
- Head freshness+2.4
- Latency−0.5
- Availability+0.0
- Correctness+0.0
The parts add to +2.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+97.7points
- Availability+40.0
- Latency*+29.5
- Correctness*+20.0
- Head freshness*+8.2
The parts add to +97.7, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.