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 Ethereum
Side by side
1h window · 60 minutes observed · generated 2026-08-27 20:33:05 UTC
| Metric | Tenderly | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 99.4 | 93.5 | 78.4 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.6 ms | 25.3 ms | 108.6 ms |
| p95 latency | 30.8 ms | 53.9 ms | 124.5 ms |
| p99 latency | 54.7 ms | 111.2 ms | 149.8 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 16 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,586 | 1,610 | 1,593 |
9 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 Tenderly, the highest scorer of those selected.
TenderlyvsPublicNode
+5.9points
- Latency+5.9
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.0points
- Latency+21.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.