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
24h window · 24 hours observed · generated 2026-10-08 18:26:19 UTC
| Metric | PublicNode | Blast API |
|---|---|---|
| Rank | 3 | 4 |
| Score | 85.9 | 76.5 |
| Status | Good | Good |
| Availability | 99.99% | 100.00% |
| p50 latency | 26.6 ms | 105.2 ms |
| p95 latency | 56.5 ms | 124.6 ms |
| p99 latency | 177.3 ms | 146.7 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 4.03 blocks | 3.30 blocks |
| Rate limited | 0 | 470 |
| Unsupported | 0 | 0 |
| Samples | 38,305 | 37,738 |
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.4points
- Latency+10.0
- Head freshness−0.6
- Availability−0.0
- Correctness−0.0
The parts add to +9.4, exactly — the score is a weighted sum, so it comes apart.