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 04:41:23 UTC
| Metric | Tenderly | NodeReal | Blast API | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 5 | 8 |
| Score | 99.2 | 86.6 | 84.0 | 58.5 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.98% | 100.00% | 99.98% | 75.73% |
| p50 latency | 19.6 ms | 87.2 ms | 104.7 ms | 2024.4 ms |
| p95 latency | 36.2 ms | 99.9 ms | 121.4 ms | 6590.4 ms |
| p99 latency | 173.2 ms | 124.2 ms | 143.0 ms | 9196.2 ms |
| Correctness | 99.99% | 100.00% | 99.99% | 96.63% |
| Head lag | 0.50 blocks | 0.34 blocks | 0.41 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 295 | 6,576 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 38,355 | 37,748 | 38,157 | 7,892 |
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
+12.6points
- Latency+12.8
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +12.6, exactly — the score is a weighted sum, so it comes apart.
TenderlyvsBlast API
+15.2points
- Latency+15.3
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +15.2, exactly — the score is a weighted sum, so it comes apart.
Tenderlyvs1RPC
+40.7points
- Latency+29.8
- Availability+9.7
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.7, exactly — the score is a weighted sum, so it comes apart.