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
7d window · 7.0 days observed · generated 2026-10-08 19:29:16 UTC
| Metric | PublicNode | Blast API |
|---|---|---|
| Rank | 3 | 4 |
| Score | 88.8 | 76.8 |
| Status | Good | Good |
| Availability | 99.96% | 99.99% |
| p50 latency | 22.9 ms | 103.3 ms |
| p95 latency | 45.8 ms | 119.4 ms |
| p99 latency | 144.1 ms | 143.6 ms |
| Correctness | 99.98% | 100.00% |
| Head lag | 4.11 blocks | 3.25 blocks |
| Rate limited | 0 | 3,580 |
| Unsupported | 0 | 0 |
| Samples | 267,056 | 262,811 |
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
+12.0points
- Latency+12.7
- Head freshness−0.7
- Availability−0.0
- Correctness−0.0
The parts add to +12.0, exactly — the score is a weighted sum, so it comes apart.