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
7d window · 3.4 days observed · generated 2026-08-28 06:38:38 UTC
| Metric | PublicNode | Blast API | 1RPC |
|---|---|---|---|
| Rank | 1 | 5 | 8 |
| Score | 99.4 | 84.4 | 61.8 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 83.57% |
| p50 latency | 19.4 ms | 105.1 ms | 265.3 ms |
| p95 latency | 35.4 ms | 122.3 ms | 4975.4 ms |
| p99 latency | 76.0 ms | 147.5 ms | 8455.9 ms |
| Correctness | 99.99% | 99.99% | 97.38% |
| Head lag | 0.49 blocks | 0.42 blocks | 0.91 blocks |
| Rate limited | 0 | 1,280 | 22,787 |
| Unsupported | 0 | 0 | 0 |
| Samples | 133,888 | 132,260 | 27,866 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsBlast API
+15.0points
- Latency+15.1
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +15.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+37.6points
- Latency+30.0
- Availability+6.6
- Correctness+0.5
- Head freshness+0.5
The parts add to +37.6, exactly — the score is a weighted sum, so it comes apart.