SuiScope
Leaderboard

BlockPI

Provider ID: blockpi

Current Snapshot

archival

Frankfurt

p50 latency

—ms

p90 latency

—ms

p99 latency

—ms

freshness

—ckpts

uptime

0.0%

error rate

100.00%

Los Angeles

p50 latency

—ms

p90 latency

—ms

p99 latency

—ms

freshness

—ckpts

uptime

0.0%

error rate

100.00%

Singapore

p50 latency

—ms

p90 latency

—ms

p99 latency

—ms

freshness

—ckpts

uptime

0.0%

error rate

100.00%

Ashburn

p50 latency

—ms

p90 latency

—ms

p99 latency

—ms

freshness

—ckpts

uptime

0.0%

error rate

100.00%

Tokyo

p50 latency

—ms

p90 latency

—ms

p99 latency

—ms

freshness

—ckpts

uptime

0.0%

error rate

100.00%

graphql

Tokyo

p50 latency

97ms

p90 latency

111ms

p99 latency

180ms

freshness

143ckpts

uptime

100.0%

error rate

0.00%

Los Angeles

p50 latency

214ms

p90 latency

250ms

p99 latency

298ms

freshness

211ckpts

uptime

100.0%

error rate

0.00%

Frankfurt

p50 latency

53ms

p90 latency

75ms

p99 latency

86ms

freshness

145ckpts

uptime

100.0%

error rate

0.00%

Ashburn

p50 latency

208ms

p90 latency

260ms

p99 latency

735ms

freshness

157ckpts

uptime

100.0%

error rate

0.00%

Singapore

p50 latency

40ms

p90 latency

65ms

p99 latency

155ms

freshness

159ckpts

uptime

100.0%

error rate

0.00%

grpc

Tokyo

p50 latency

115ms

p90 latency

267ms

p99 latency

287ms

freshness

0ckpts

uptime

100.0%

error rate

0.00%

Singapore

p50 latency

50ms

p90 latency

67ms

p99 latency

102ms

freshness

0ckpts

uptime

100.0%

error rate

0.00%

Ashburn

p50 latency

133ms

p90 latency

231ms

p99 latency

1546ms

freshness

0ckpts

uptime

100.0%

error rate

0.00%

Frankfurt

p50 latency

61ms

p90 latency

84ms

p99 latency

138ms

freshness

0ckpts

uptime

100.0%

error rate

0.00%

Los Angeles

p50 latency

101ms

p90 latency

122ms

p99 latency

129ms

freshness

0ckpts

uptime

100.0%

error rate

0.00%

Time Series

About these measurements

Measurements are independently collected by SuiScope from multiple regions. They represent observed public-endpoint performance, not the provider's total infrastructure capacity. See the methodology for definitions and limitations.