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 19:42:58 UTC
| Metric | dRPC | NodeReal | Blast API |
|---|---|---|---|
| Rank | 3 | 4 | 5 |
| Score | 91.0 | 86.6 | 83.8 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 100.00% | 99.97% |
| p50 latency | 33.7 ms | 87.4 ms | 106.3 ms |
| p95 latency | 70.8 ms | 100.0 ms | 123.3 ms |
| p99 latency | 175.6 ms | 129.5 ms | 151.2 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.34 blocks | 0.41 blocks |
| Rate limited | 133 | 0 | 304 |
| Unsupported | 0 | 0 | 0 |
| Samples | 37,798 | 37,795 | 38,317 |
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.
dRPCvsNodeReal
+4.4points
- Latency+4.4
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.4, exactly — the score is a weighted sum, so it comes apart.
dRPCvsBlast API
+7.1points
- Latency+7.1
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +7.1, exactly — the score is a weighted sum, so it comes apart.