Live  /  Providers  /  BlockPI

BlockPI

blockpi.ioNo open incidents

Independent assessment — SquidGrid is not affiliated with BlockPI. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks BlockPI’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what BlockPI is reporting

Current & recent incidents

Resolved

Abstract Mainnet service discontinue notice

Minor impact · 2026-11-11 06:39 UTC · source

Resolved

Polygon Amoy rpc service is down due to the Uburu Hard Fork

Critical impact · 2026-11-05 17:04 UTC · source

Resolved

Cosmos is experiencing a chain-level outage

Major impact · 2026-09-23 15:56 UTC · source

Resolved

cosmos rpc service is down

Critical impact · 2026-09-09 03:56 UTC · source

Resolved

The cronos archive node has gone down.

Critical impact · 2026-09-02 02:41 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 5 incidents from BlockPI’s own status page since 2026-09-02.

Recent incidents in the archive

Computed by SquidGrid from the incidents BlockPI published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what BlockPI has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

BlockPI runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of BlockPI is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with BlockPI.