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-26 22:54:10 UTC
| Metric | PublicNode | Tenderly | Blast API |
|---|---|---|---|
| Rank | 1 | 2 | 5 |
| Score | 99.4 | 98.8 | 84.2 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.97% | 99.98% |
| p50 latency | 18.6 ms | 19.8 ms | 104.2 ms |
| p95 latency | 34.7 ms | 37.4 ms | 120.9 ms |
| p99 latency | 72.4 ms | 256.8 ms | 140.2 ms |
| Correctness | 99.99% | 99.99% | 99.98% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.42 blocks |
| Rate limited | 0 | 0 | 358 |
| Unsupported | 0 | 0 | 0 |
| Samples | 39,026 | 38,751 | 38,555 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsTenderly
+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.
PublicNodevsBlast API
+15.2points
- Latency+15.3
- Head freshness−0.1
- Correctness+0.0
- Availability−0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.