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:00:30 UTC
| Metric | NodeReal | BNB Chain | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 97.8 | 95.8 | 67.2 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.8 ms | 17.7 ms | 111.1 ms |
| p95 latency | 25.2 ms | 24.8 ms | 130.2 ms |
| p99 latency | 54.0 ms | 42.6 ms | 147.3 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 1.70 blocks | 4.35 blocks | 2.59 blocks |
| Rate limited | 0 | 31 | 19 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,580 | 3,237 | 1,603 |
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.3
- Latency−0.3
- Availability+0.0
- Correctness+0.0
The parts add to +2.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+30.6points
- Latency+29.7
- Head freshness+0.8
- Availability+0.0
- Correctness+0.0
The parts add to +30.6, exactly — the score is a weighted sum, so it comes apart.