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
1h window · 60 minutes observed · generated 2026-08-28 09:12:39 UTC
| Metric | Tenderly | NodeReal | Blast API |
|---|---|---|---|
| Rank | 1 | 3 | 5 |
| Score | 99.4 | 81.6 | 78.3 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 100.00% | 99.87% |
| p50 latency | 18.6 ms | 86.3 ms | 105.4 ms |
| p95 latency | 32.9 ms | 99.4 ms | 120.3 ms |
| p99 latency | 58.4 ms | 126.1 ms | 132.3 ms |
| Correctness | 99.94% | 100.00% | 99.93% |
| Head lag | 0.46 blocks | 0.35 blocks | 0.39 blocks |
| Rate limited | 0 | 0 | 48 |
| Unsupported | 0 | 0 | 0 |
| Samples | 1,612 | 1,590 | 1,610 |
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
+17.9points
- Latency+18.0
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +17.9, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+21.1points
- Latency+21.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +21.1, exactly — the score is a weighted sum, so it comes apart.