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-28 00:17:11 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.4 | 83.8 | 78.0 | 53.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.97% | 100.00% | 62.50% |
| p50 latency | 33.1 ms | 106.2 ms | 107.6 ms | 2668.5 ms |
| p95 latency | 68.8 ms | 123.6 ms | 193.1 ms | 8458.8 ms |
| p99 latency | 173.1 ms | 151.1 ms | 238.0 ms | 9776.0 ms |
| Correctness | 99.99% | 100.00% | 100.00% | 98.13% |
| Head lag | 0.36 blocks | 0.41 blocks | 0.52 blocks | 0.97 blocks |
| Rate limited | 116 | 270 | 6,010 | 6,435 |
| Unsupported | 0 | 0 | 74 | 0 |
| Samples | 37,112 | 37,706 | 8,781 | 7,531 |
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
+7.6points
- Latency+7.5
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.4points
- Latency+13.2
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+37.9points
- Latency+21.9
- Availability+15.0
- Head freshness+0.7
- Correctness+0.4
The parts add to +37.9, exactly — the score is a weighted sum, so it comes apart.