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 | PublicNode | Blast API |
|---|---|---|
| Rank | 3 | 4 |
| Score | 81.5 | 67.2 |
| Status | Good | Degraded |
| Availability | 100.00% | 100.00% |
| p50 latency | 30.1 ms | 111.1 ms |
| p95 latency | 54.2 ms | 130.2 ms |
| p99 latency | 195.9 ms | 147.3 ms |
| Correctness | 100.00% | 100.00% |
| Head lag | 3.52 blocks | 2.59 blocks |
| Rate limited | 0 | 19 |
| Unsupported | 0 | 0 |
| Samples | 1,619 | 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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+14.2points
- Latency+15.0
- Head freshness−0.8
- Availability+0.0
- Correctness+0.0
The parts add to +14.2, exactly — the score is a weighted sum, so it comes apart.