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 22:56:49 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 2 | 3 | 4 |
| Score | 95.6 | 88.7 | 82.5 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.99% | 99.97% |
| p50 latency | 23.6 ms | 34.1 ms | 87.1 ms |
| p95 latency | 46.5 ms | 69.5 ms | 99.0 ms |
| p99 latency | 102.9 ms | 190.6 ms | 117.9 ms |
| Correctness | 100.00% | 100.00% | 99.97% |
| Head lag | 0.47 blocks | 0.35 blocks | 0.33 blocks |
| Rate limited | 0 | 19 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 9,725 | 9,490 | 9,475 |
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
+6.9points
- Latency+7.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+13.1points
- Latency+13.2
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +13.1, exactly — the score is a weighted sum, so it comes apart.