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
24h window · 24 hours observed · generated 2026-08-27 03:18:01 UTC
| Metric | PublicNode | dRPC | NodeReal |
|---|---|---|---|
| Rank | 1 | 3 | 4 |
| Score | 99.4 | 91.0 | 86.6 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.92% | 100.00% |
| p50 latency | 18.4 ms | 34.1 ms | 87.2 ms |
| p95 latency | 35.3 ms | 70.1 ms | 99.9 ms |
| p99 latency | 74.4 ms | 172.3 ms | 124.6 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.34 blocks |
| Rate limited | 0 | 128 | 0 |
| Unsupported | 0 | 0 | 0 |
| Samples | 38,036 | 37,138 | 37,111 |
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.4points
- Latency+8.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+12.8points
- Latency+13.0
- Head freshness−0.2
- Availability−0.0
- Correctness+0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.