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
6h window · 6.0 hours observed · generated 2026-08-27 04:37:14 UTC
| Metric | Tenderly | PublicNode | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 99.2 | 59.0 |
| Status | Excellent | Excellent | Degraded |
| Availability | 100.00% | 99.99% | 76.94% |
| p50 latency | 18.5 ms | 17.4 ms | 2024.4 ms |
| p95 latency | 32.1 ms | 33.0 ms | 6590.4 ms |
| p99 latency | 66.5 ms | 75.1 ms | 9196.2 ms |
| Correctness | 100.00% | 100.00% | 96.63% |
| Head lag | 0.48 blocks | 0.49 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 1,543 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,080 | 9,181 | 2,125 |
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.2points
- Latency+0.2
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.4points
- Latency+30.0
- Availability+9.2
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.4, exactly — the score is a weighted sum, so it comes apart.