BlockPI had 41 outages in the last 2 years totaling 2169h 23m of downtime — averaging 1.7 incidents per month.
There were 41 BlockPI outages since April 23, 2025 totaling 2169h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.
Due to berachain hardfork and the berachain RPC service has been suspended. We apologize for any inconvenience this may cause. link: https://x.com/berachain/status/1985288599152042101
This incident has been resolved.
Our Arbitrum mainnet archive RPC service is currently down. We are working hard to restore it. We apologize for the inconvenience.
This incident has been resolved.
Due to a failed Linea version upgrade, the node data has been corrupted, so the Linea archive RPC service has been suspended. We apologize for any inconvenience this may cause.
This incident has been resolved.
Due to a block synchronization issue, the Flow-evm mainnet rpc service has been suspended. We are actively working to resolve the problem and sincerely apologize for the inconvenience caused.
This incident has been resolved.
Due to a block synchronization issue, the Linea mainnet rpc service has been suspended. We are actively working to resolve the problem and sincerely apologize for the inconvenience caused.
The Linea full rpc service has been restored, but the Linea archive rpc service is still synchronizing.
This incident has been resolved.
Our BSC archive node has experienced data corruption and is currently under repair. We apologize for the inconvenience caused.
This incident has been resolved.
Our Linea Sepolia experienced data corruption due to a failed upgrade process and is currently under repair. We apologize for the inconvenience caused.
This incident has been resolved.
We are going to perform a scheduled Linea Sepolia node upgrade. During the upgrade, there may be major service interruptions. For more details about this upgrade, please check: https://docs.linea.build/get-started/how-to/run-a-node/beta-v4-migration
This incident has been resolved.
0g-galileo network paused. We are closely monitoring the latest developments of this network. Once the network is restored, we will repair it as quickly as possible. For more details about this issue, please check: https://discord.com/channels/1210423309808963594/1226951487272255498/1418494590675058769 https://chainscan-galileo.0g.ai/blocks
This incident has been resolved.
Our Story nodes had an sync issue with the latest hardforks. We are working on solve it.
This incident has been resolved.
Due to a data error on the Xlayer, there are synchronization issues with all nodes of this chain operated by All 3rd-party RPC service providers. We are working with the official team to resolve the issue as quickly as possible. We sincerely apologize for the inconvenience caused
We are continuing to investigate this issue.
This incident has been resolved.
We are going to perform a scheduled Mantle Prague upgrade. During the upgrade, the node service will be temporarily unavailable until the upgrade is complete. This upgrade requires log index head rendering, which extends the downtime; it is expected to take approximately 10 hours. We apologize for any inconvenience caused. For more details about this upgrade, please check: https://github.com/mantlenetworkio/op-geth/releases/tag/v1.3.1
This incident has been resolved.
The Polygon mainnet is currently unavailable due to Erigon client issues that have caused the chaindata to become corrupted. We are working to restore the data and the RPC service as soon as possible.
This incident has been resolved.
We're currently addressing data corruption affecting NEAR Testnet nodes. Service restoration efforts are underway. We apologize for any operational disruptions this may cause.
This incident has been resolved.
The Polygon mainnet is currently unavailable due to client issues that have caused the chaindata to become corrupted. We are working to restore the data and the RPC service as soon as possible.
We are continuing to work on a fix for this issue.
The Polygon mainnet is currently unavailable due to Erigon client issues that have caused the chaindata to become corrupted. We are working to restore the data and the RPC service as soon as possible.
This incident has been resolved.
Due to a data error on the polygon-zkevm, there are synchronization issues with all nodes of this chain operated by BlockPI. We are actively communicating with the chain's officials and working to resolve the issue as quickly as possible. We sincerely apologize for the inconvenience caused.
This incident has been resolved.