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— showing the top 4 by score. Click to change.
Side by side
7d window · 7.0 days observed · generated 2026-10-08 16:37:52 UTC
| Metric | PublicNode | Tenderly | NodeReal | dRPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 4 |
| Score | 99.4 | 98.4 | 83.7 | 81.0 |
| Status | Excellent | Excellent | Good | Good |
| Availability | 99.98% | 99.99% | 99.98% | 99.97% |
| p50 latency | 21.3 ms | 26.9 ms | 87.2 ms | 33.0 ms |
| p95 latency | 44.9 ms | 49.1 ms | 99.4 ms | 113.1 ms |
| p99 latency | 181.2 ms | 70.5 ms | 123.9 ms | 200.7 ms |
| Correctness | 99.98% | 99.99% | 99.99% | 99.99% |
| Head lag | 0.45 blocks | 0.44 blocks | 0.35 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 0 | 1,338 |
| Unsupported | 0 | 0 | 0 | 71 |
| Samples | 262,302 | 260,469 | 255,858 | 255,691 |
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
+1.1points
- Latency+1.1
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +1.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+15.7points
- Latency+15.8
- Head freshness−0.1
- Correctness−0.0
- Availability−0.0
The parts add to +15.7, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+18.5points
- Latency+18.5
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +18.5, exactly — the score is a weighted sum, so it comes apart.