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 19:13:18 UTC
| Metric | PublicNode | Tenderly | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 98.2 | 64.7 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.96% | 90.50% |
| p50 latency | 18.9 ms | 20.0 ms | 259.6 ms |
| p95 latency | 33.4 ms | 39.4 ms | 2579.7 ms |
| p99 latency | 70.9 ms | 409.4 ms | 4625.5 ms |
| Correctness | 99.98% | 99.98% | 98.18% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 6,467 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,913 | 37,675 | 7,742 |
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
+1.2points
- Latency+1.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +1.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+34.7points
- Latency+30.0
- Availability+3.8
- Head freshness+0.5
- Correctness+0.4
The parts add to +34.7, exactly — the score is a weighted sum, so it comes apart.