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-26 22:04:01 UTC
| Metric | PublicNode | dRPC | 1RPC |
|---|---|---|---|
| Rank | 1 | 3 | 8 |
| Score | 99.4 | 91.3 | 64.4 |
| Status | Excellent | Excellent | Degraded |
| Availability | 99.98% | 99.93% | 89.75% |
| p50 latency | 18.7 ms | 34.1 ms | 259.6 ms |
| p95 latency | 34.7 ms | 68.5 ms | 2579.7 ms |
| p99 latency | 72.1 ms | 168.4 ms | 4625.5 ms |
| Correctness | 99.99% | 99.99% | 98.18% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.94 blocks |
| Rate limited | 0 | 120 | 6,403 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,671 | 36,782 | 7,676 |
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.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+35.0points
- Latency+30.0
- Availability+4.1
- Head freshness+0.5
- Correctness+0.4
The parts add to +35.0, exactly — the score is a weighted sum, so it comes apart.