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
24h window · 24 hours observed · generated 2026-08-27 13:38:25 UTC
| Metric | Tenderly | PublicNode | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 99.4 | 98.8 | 83.8 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.97% | 99.99% |
| p50 latency | 19.3 ms | 19.4 ms | 105.7 ms |
| p95 latency | 34.4 ms | 37.3 ms | 122.5 ms |
| p99 latency | 83.7 ms | 86.7 ms | 149.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.41 blocks |
| Rate limited | 0 | 0 | 331 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,258 | 38,618 | 38,068 |
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
+0.6points
- Latency+0.6
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +0.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.6points
- Latency+15.7
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.6, exactly — the score is a weighted sum, so it comes apart.