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
7d window · 2.7 days observed · generated 2026-08-27 12:22:33 UTC
| Metric | PublicNode | Tenderly | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 95.7 | 62.5 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.97% | 99.96% | 85.16% |
| p50 latency | 18.6 ms | 19.8 ms | 225.7 ms |
| p95 latency | 34.0 ms | 55.9 ms | 4391.3 ms |
| p99 latency | 72.2 ms | 793.0 ms | 7602.5 ms |
| Correctness | 99.99% | 99.99% | 97.48% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.91 blocks |
| Rate limited | 0 | 0 | 17,721 |
| Unsupported | 0 | 0 | 0 |
| Samples | 104,021 | 103,225 | 21,710 |
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
+3.7points
- Latency+3.7
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+36.9points
- Latency+30.0
- Availability+5.9
- Correctness+0.5
- Head freshness+0.5
The parts add to +36.9, exactly — the score is a weighted sum, so it comes apart.