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-08 18:27:13 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 86.0 | 76.3 | 27.3 |
| Status | Good | Good | Poor |
| Availability | 99.98% | 99.99% | 7.96% |
| p50 latency | 30.2 ms | 110.8 ms | 1438.6 ms |
| p95 latency | 57.2 ms | 129.5 ms | 7334.3 ms |
| p99 latency | 203.5 ms | 157.5 ms | 8983.2 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 4.00 blocks | 3.35 blocks | 7.01 blocks |
| Rate limited | 0 | 112 | 917 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,898 | 8,746 | 4,480 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+9.7points
- Latency+10.2
- Head freshness−0.5
- Availability−0.0
- Correctness−0.0
The parts add to +9.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+58.7points
- Availability+36.8
- Latency+20.0
- Head freshness+1.9
- Correctness−0.0
The parts add to +58.7, exactly — the score is a weighted sum, so it comes apart.