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:13:28 UTC
| Metric | NodeReal | BNB Chain | PublicNode | Blast API |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 97.4 | 95.6 | 81.1 | 66.7 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 99.94% | 100.00% |
| p50 latency | 17.9 ms | 17.7 ms | 30.0 ms | 110.8 ms |
| p95 latency | 25.4 ms | 24.4 ms | 53.8 ms | 130.3 ms |
| p99 latency | 54.0 ms | 40.1 ms | 204.8 ms | 159.0 ms |
| Correctness | 100.00% | 100.00% | 99.94% | 100.00% |
| Head lag | 1.65 blocks | 4.67 blocks | 3.97 blocks | 3.21 blocks |
| Rate limited | 0 | 30 | 0 | 18 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 1,584 | 3,228 | 1,612 | 1,600 |
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.6
- Latency−0.7
- 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.3points
- Latency+14.3
- Head freshness+2.0
- Availability+0.0
- Correctness+0.0
The parts add to +16.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+30.7points
- Latency+29.3
- Head freshness+1.4
- Availability+0.0
- Correctness+0.0
The parts add to +30.7, exactly — the score is a weighted sum, so it comes apart.