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 14:03:16 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 90.6 | 83.8 | 77.8 | 57.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.92% | 99.99% | 100.00% | 73.97% |
| p50 latency | 33.9 ms | 105.6 ms | 107.1 ms | 2024.4 ms |
| p95 latency | 71.8 ms | 122.0 ms | 193.5 ms | 6590.4 ms |
| p99 latency | 171.8 ms | 148.4 ms | 234.3 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 96.63% |
| Head lag | 0.37 blocks | 0.41 blocks | 0.50 blocks | 0.95 blocks |
| Rate limited | 147 | 331 | 5,902 | 6,405 |
| Unsupported | 0 | 0 | 68 | 0 |
| Samples | 36,744 | 37,122 | 8,504 | 7,699 |
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 dRPC, the highest scorer of those selected.
dRPCvsBlast API
+6.8points
- Latency+6.7
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.7points
- Latency+12.6
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +12.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+32.8points
- Latency+21.0
- Availability+10.4
- Correctness+0.7
- Head freshness+0.7
The parts add to +32.8, exactly — the score is a weighted sum, so it comes apart.