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:21:12 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 88.8 | 76.8 | 30.0 |
| Status | Good | Good | Poor |
| Availability | 99.96% | 99.99% | 16.28% |
| p50 latency | 22.9 ms | 103.3 ms | 494.5 ms |
| p95 latency | 45.8 ms | 119.4 ms | 6063.9 ms |
| p99 latency | 144.1 ms | 143.5 ms | 9149.9 ms |
| Correctness | 99.98% | 100.00% | 99.63% |
| Head lag | 4.11 blocks | 3.25 blocks | 8.31 blocks |
| Rate limited | 0 | 3,574 | 40,525 |
| Unsupported | 0 | 0 | 1 |
| Samples | 266,835 | 262,595 | 65,369 |
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.
PublicNodevs1RPC
+58.9points
- Availability+33.5
- Latency+22.9
- Head freshness+2.4
- Correctness+0.1
The parts add to +58.9, exactly — the score is a weighted sum, so it comes apart.