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 06:53:58 UTC
| Metric | PublicNode | Tenderly | NodeReal |
|---|---|---|---|
| Rank | 1 | 2 | 4 |
| Score | 99.4 | 98.9 | 80.4 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 100.00% | 99.99% |
| p50 latency | 17.8 ms | 18.7 ms | 87.1 ms |
| p95 latency | 30.6 ms | 32.2 ms | 103.1 ms |
| p99 latency | 54.8 ms | 64.8 ms | 138.2 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 0.48 blocks | 0.47 blocks | 0.35 blocks |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,630 | 9,545 | 9,415 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsTenderly
+0.5points
- Latency+0.5
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +0.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+19.0points
- Latency+19.2
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +19.0, exactly — the score is a weighted sum, so it comes apart.