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
1h window · 60 minutes observed · generated 2026-08-27 13:06:11 UTC
| Metric | Tenderly | PublicNode | NodeReal |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 99.4 | 95.4 | 82.5 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 20.2 ms | 25.2 ms | 88.0 ms |
| p95 latency | 32.2 ms | 47.1 ms | 99.4 ms |
| p99 latency | 58.8 ms | 101.1 ms | 123.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.48 blocks | 0.32 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,610 | 1,618 | 1,568 |
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
+4.0points
- Latency+4.0
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +4.0, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsNodeReal
+16.9points
- Latency+17.1
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +16.9, exactly — the score is a weighted sum, so it comes apart.