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 10:16:51 UTC
| Metric | Tenderly | PublicNode | NodeReal |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 99.4 | 99.0 | 80.7 |
| Status | Excellent | Excellent | Good |
| Availability | 99.93% | 99.98% | 100.00% |
| p50 latency | 19.2 ms | 20.1 ms | 87.9 ms |
| p95 latency | 34.1 ms | 35.5 ms | 106.2 ms |
| p99 latency | 133.2 ms | 91.1 ms | 143.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.49 blocks | 0.35 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,538 | 8,612 | 8,416 |
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.4points
- Latency+0.4
- Availability−0.0
- Head freshness+0.0
- Correctness+0.0
The parts add to +0.4, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+18.7points
- Latency+18.9
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +18.7, exactly — the score is a weighted sum, so it comes apart.