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-28 00:17:41 UTC
| Metric | Tenderly | PublicNode | 1RPC |
|---|---|---|---|
| Rank | 1 | 2 | 8 |
| Score | 99.4 | 97.7 | 53.8 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.99% | 63.48% |
| p50 latency | 19.2 ms | 21.8 ms | 2490.1 ms |
| p95 latency | 33.0 ms | 41.5 ms | 8458.8 ms |
| p99 latency | 70.2 ms | 98.2 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 98.26% |
| Head lag | 0.47 blocks | 0.48 blocks | 1.03 blocks |
| Rate limited | 0 | 0 | 6,436 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,752 | 38,076 | 7,542 |
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
+1.7points
- Latency+1.7
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+45.6points
- Latency+30.0
- Availability+14.6
- Head freshness+0.6
- Correctness+0.3
The parts add to +45.6, exactly — the score is a weighted sum, so it comes apart.