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-27 20:22:01 UTC
| Metric | Tenderly | PublicNode | NodeReal |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 99.4 | 97.8 | 86.6 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.99% | 100.00% |
| p50 latency | 19.2 ms | 21.2 ms | 87.3 ms |
| p95 latency | 33.1 ms | 41.4 ms | 99.9 ms |
| p99 latency | 74.9 ms | 102.4 ms | 128.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.48 blocks | 0.34 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,823 | 38,191 | 37,240 |
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
- Availability−0.0
- Head freshness+0.0
- Correctness−0.0
The parts add to +1.7, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+12.8points
- Latency+12.9
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.