Fireblocks incident
FB526U: Issues with login to Fireblocks Console and Transactions
Fireblocks experienced a major incident on June 7, 2026 affecting Transactions engine and Web console, lasting 4h 28m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 07, 2026, 10:34 AM UTC
We are currently investigating this issue.
- investigating Jun 07, 2026, 10:36 AM UTC
We are continuing to investigate this issue.
- identified Jun 07, 2026, 10:53 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jun 07, 2026, 11:41 AM UTC
A fix has been implemented and we are monitoring the results. New instances are operational. We are working on any collateral that this issue may have caused.
- resolved Jun 07, 2026, 03:06 PM UTC
This incident has been resolved.
- postmortem Jun 25, 2026, 07:11 AM UTC
* **The Issue:** On June 7, 2026, an automated maintenance error accidentally deleted a critical production database, temporarily disrupting console logins and transaction processing. * **The Resolution:** Fireblocks immediately identified the issue, activated our disaster recovery protocols, and fully restored all platform services. * **Our Commitment:** Additional remediation measures have been taken to support affected customers and prevent this specific automation error from recurring.