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
7d window · 2.7 days observed · generated 2026-08-27 12:28:57 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 99.4 | 92.4 | 87.9 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.93% | 99.82% |
| p50 latency | 18.6 ms | 33.8 ms | 87.4 ms |
| p95 latency | 34.0 ms | 72.2 ms | 100.0 ms |
| p99 latency | 72.2 ms | 168.5 ms | 125.7 ms |
| Correctness | 99.99% | 99.99% | 99.99% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.35 blocks |
| Rate limited | 0 | 637 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 104,193 | 101,700 | 101,661 |
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
+7.0points
- Latency+7.2
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+11.5points
- Latency+11.6
- Head freshness−0.2
- Availability+0.1
- Correctness−0.0
The parts add to +11.5, exactly — the score is a weighted sum, so it comes apart.