
Fireblocks Status
Fireblocks is currently operational with all systems functioning normally.
Incident History
Showing incidents from the last 15 days
Report: "FB527U: Intermittent delays with SUI outgoing transactions"
Last updateThis incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Our transaction processing infrastructure SUI network is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
Report: "FB526U: Issues with login to Fireblocks Console and Transactions"
Last updateThe issue has been identified and a fix is being implemented.
We are continuing to investigate this issue.
We are currently investigating this issue.
Report: "FB525U: Intermittent delays with TON transactions"
Last updateOur TON transaction processing infrastructure is experiencing an issue that is delaying incoming transaction notifications, and stalling of outgoing transactions. We are actively investigating this issue.
Report: "FB524U: Intermittent delays with updating transaction statuses and balance on Fireblocks console"
Last updateA fix has been implemented and we are monitoring the results.
Transactions are being signed and processed as expected on-chain - the issue is isolated to the web console only. We are actively investigating this issue.
The issue has been identified and a fix is being implemented.
Our Fireblocks web console is currently experiencing an issue that is causing Intermittent delays with updating transaction statuses and balance. We are actively investigating this issue.
Report: "FB523U: Transactions and balance updates issues on Kusama blockchain"
Last updateA fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on Kusama blockchain. We are actively investigating this issue.