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
30d window · 3.5 days observed · generated 2026-08-28 07:43:11 UTC
| Metric | dRPC | Blast API | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 5 | 6 | 8 |
| Score | 91.5 | 84.3 | 78.2 | 61.8 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.94% | 99.98% | 99.99% | 83.57% |
| p50 latency | 33.7 ms | 105.1 ms | 106.7 ms | 265.3 ms |
| p95 latency | 70.7 ms | 122.2 ms | 194.9 ms | 4975.4 ms |
| p99 latency | 171.7 ms | 147.4 ms | 244.8 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 100.00% | 97.38% |
| Head lag | 0.36 blocks | 0.42 blocks | 0.49 blocks | 0.91 blocks |
| Rate limited | 685 | 1,330 | 21,640 | 23,089 |
| Unsupported | 0 | 0 | 266 | 0 |
| Samples | 132,362 | 134,005 | 31,287 | 28,212 |
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.2points
- Latency+7.1
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +7.2, 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
+29.7points
- Latency+22.0
- Availability+6.6
- Head freshness+0.6
- Correctness+0.5
The parts add to +29.7, exactly — the score is a weighted sum, so it comes apart.