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
6h window · 6.0 hours observed · generated 2026-10-09 01:04:36 UTC
| Metric | NodeReal | BNB Chain | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 4 | 5 |
| Score | 97.8 | 95.6 | 76.7 | 35.2 |
| Status | Excellent | Excellent | Good | Poor |
| Availability | 100.00% | 100.00% | 99.99% | 28.14% |
| p50 latency | 19.5 ms | 18.9 ms | 104.7 ms | 1857.3 ms |
| p95 latency | 26.5 ms | 25.8 ms | 117.5 ms | 7100.6 ms |
| p99 latency | 46.5 ms | 41.0 ms | 134.3 ms | 9702.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 1.71 blocks | 4.57 blocks | 3.36 blocks | 7.36 blocks |
| Rate limited | 0 | 164 | 122 | 1,259 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,095 | 16,595 | 8,101 | 2,330 |
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.1points
- Head freshness+2.4
- Latency−0.3
- Availability+0.0
- Correctness+0.0
The parts add to +2.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsBlast API
+21.1points
- Latency+19.6
- Head freshness+1.5
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+62.5points
- Latency+29.7
- Availability+28.7
- Head freshness+4.1
- Correctness+0.0
The parts add to +62.5, exactly — the score is a weighted sum, so it comes apart.