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
30d window · 30.0 days observed · generated 2026-10-08 18:27:14 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 91.0 | 76.8 | 34.8 |
| Status | Excellent | Good | Poor |
| Availability | 99.92% | 99.71% | 37.62% |
| p50 latency | 21.9 ms | 104.5 ms | 831.2 ms |
| p95 latency | 43.1 ms | 124.3 ms | 6724.2 ms |
| p99 latency | 112.7 ms | 392.5 ms | 9350.5 ms |
| Correctness | 99.99% | 99.99% | 98.79% |
| Head lag | 4.19 blocks | 3.31 blocks | 2671.14 blocks |
| Rate limited | 0 | 15,866 | 192,444 |
| Unsupported | 0 | 0 | 6 |
| Samples | 1,166,275 | 1,143,423 | 249,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.1points
- Latency+14.8
- Head freshness−0.7
- Availability+0.1
- Correctness−0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+56.2points
- Latency+25.1
- Availability+24.9
- Head freshness+5.9
- Correctness+0.2
The parts add to +56.2, exactly — the score is a weighted sum, so it comes apart.