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
6h window · 6.0 hours observed · generated 2026-08-28 05:32:48 UTC
| Metric | Tenderly | NodeReal | Blast API |
|---|---|---|---|
| Rank | 2 | 4 | 5 |
| Score | 99.2 | 85.7 | 83.8 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 99.63% | 99.99% |
| p50 latency | 17.8 ms | 87.6 ms | 103.7 ms |
| p95 latency | 30.7 ms | 98.8 ms | 117.2 ms |
| p99 latency | 52.2 ms | 114.4 ms | 142.9 ms |
| Correctness | 100.00% | 100.00% | 99.99% |
| Head lag | 0.47 blocks | 0.34 blocks | 0.40 blocks |
| Rate limited | 0 | 0 | 42 |
| Unsupported | 0 | 0 | 0 |
| Samples | 8,989 | 8,818 | 8,992 |
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 Tenderly, the highest scorer of those selected.
TenderlyvsNodeReal
+13.5points
- Latency+13.5
- Head freshness−0.2
- Availability+0.1
- Correctness+0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.5points
- Latency+15.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +15.5, exactly — the score is a weighted sum, so it comes apart.