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:27:00 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 80.9 | 66.8 | 0.0 |
| Status | Good | Degraded | Poor |
| Availability | 99.94% | 100.00% | 0.00% |
| p50 latency | 29.9 ms | 110.4 ms | 0.0 ms |
| p95 latency | 54.9 ms | 130.4 ms | 0.0 ms |
| p99 latency | 223.7 ms | 159.1 ms | 0.0 ms |
| Correctness | 99.94% | 100.00% | not measured |
| Head lag | 3.78 blocks | 3.09 blocks | no cohort |
| Rate limited | 0 | 18 | 271 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,628 | 1,619 | 324 |
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.7
- Head freshness−0.6
- Availability−0.0
- Correctness−0.0
The parts add to +14.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+80.9points
- Availability+40.0
- Correctness*+20.0
- Latency*+14.7
- Head freshness*+6.2
The parts add to +80.9, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.