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-28 00:02:54 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 99.4 | 91.2 | 85.7 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 17.7 ms | 31.7 ms | 87.3 ms |
| p95 latency | 29.2 ms | 61.2 ms | 98.8 ms |
| p99 latency | 52.3 ms | 148.1 ms | 111.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.40 blocks | 0.36 blocks |
| Rate limited | 0 | 2 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,629 | 1,578 | 1,580 |
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.
PublicNodevsdRPC
+8.2points
- Latency+8.3
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+13.7points
- Latency+13.9
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +13.7, exactly — the score is a weighted sum, so it comes apart.