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-27 12:25:41 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 2 | 3 | 4 |
| Score | 95.5 | 86.7 | 83.0 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.94% | 100.00% |
| p50 latency | 24.7 ms | 34.0 ms | 87.3 ms |
| p95 latency | 48.7 ms | 80.0 ms | 98.8 ms |
| p99 latency | 101.1 ms | 193.6 ms | 120.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.38 blocks | 0.33 blocks |
| Rate limited | 0 | 10 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,622 | 1,587 | 1,582 |
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.8points
- Latency+8.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+12.5points
- Latency+12.7
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.