Fireblocks
Apps and SaaS. Source: Fireblocks status page.
- Incidents, last 90 days
- 19
- Median to mitigation
- 32m
- Median to resolution
- 39m
- p95 to resolution
- 28h 57m
- Naming an upstream provider
- 0%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 10 |
| The text does not say enough to tell | 5 |
| A provider or third-party service this vendor depends on failed | 2 |
| Login, tokens, certificates or credentials failed | 2 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
FB561U: Delayed Webhook notifications and new webhook creation
Affected: Webhooks
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Webhook(s) processing infrastructure is currently experiencing an issue causing a delay in sending the Webhook(s). We are actively investigating this issue. Webhooks that were sent during the incident could have a slight delay in arriving
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB560U: Transactions and balance updates issues on Ripple blockchain
Affected: Ripple
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on Ripple blockchain. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB559U: Transaction Processing Issue
Affected: Transactions engine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this delay in transaction processing.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB558U: Plasma Node Issues
Affected: Plasma
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB557U: Delay in processing wallet balance updates
Affected: Web console, API
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating and issue with a delay in balance updates on the platform.
-
investigating
We are continuing to investigate this issue.
-
identified
The short delay in balance updates is improved.
-
monitoring
Balances are updating as expected.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB556U: Transaction issues on Cardano blockchain
Affected: Transactions engine
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing transaction statuses for Cardano transactions.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB555U: ETH Missing or Confirming Transactions, and Balance Gap
Affected: Transactions engine
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB554U: Transactions issues on Ethereum blockchain
Affected: Transactions engine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on ETH blockchain. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB553U: Intermittent delays with Ripple transactions
Affected: Ripple
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing Ripple transaction statuses. We are actively investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB552U: Blockchain Mantra is halted
Affected: Mantra
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
identified
Mantra blockchain is halted, you can track the foundation status page here: https://status.mantrachain.io/ Please note that the issue is related to the blockchain itself and not Fireblocks infrastructure. Due to this, Fireblocks halted Mantra as well. It will be resumed once the...
-
identified
We are continuing to work on a fix for this issue.
-
monitoring
A fix has been implemented by MANTRA and we are monitoring the chain.
-
resolved
This incident has been resolved. We have resumed the network activities.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB551U: THOR Chain (RUNE_THOR) Transactions Are Blocked on Fireblocks Platform due to THOR Node Infrastructure Issues
Affected: THORChain
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB550U: Issues with login to Fireblocks Console
Affected: Web console
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our login infrastructure is currently experiencing an issue that is causing login failures for Console users. We are currently investigating this issue
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB549U: Transaction Processing Issue
Affected: Transactions engine, Web console, API
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue with transaction processing.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB548U: Intermittent delays with TON transactions
Affected: TON
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our TON transaction processing infrastructure is experiencing an issue that is delaying incoming transaction notifications, and stalling of outgoing transactions.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB547U: Degradation in the Transaction Engine
Affected: Transactions engine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB546U: Intermittent delays with Ripple transactions
Affected: Ripple
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status for Ripple transactions. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB545U: Intermittent delays with Robinhood chain transactions
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB544U: Authentication Issues with Fireblocks
Affected: User authentication
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our authentication infrastructure is currently experiencing an issue that is causing login failures for users. We are currently investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB543U: Intermittent delays with updating transactions statues on Fireblocks console
Affected: Web console
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Fireblocks console is currently experiencing an issue that is causing Intermittent delays with updating the transaction statuses on Fireblocks console. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB542U: policy page not loading in the console
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our infrastructure is experiencing an issue causing failures when accessing the policy page in the console. We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB541U: Transaction issues on Cardano blockchain
Affected: Cardano
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing transaction statuses for Cardano transactions. Symptoms include outgoing transactions stuck in BROADCASTING status, we are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB540U:Transactions issues with outgoing transactions
Affected: Transactions engine
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue which is causing a delay in finalizing the transaction status. Symptoms include delayed notification for transactions approvals on Mobile device and cosigner and also transactions stuck in diffrent...
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB539U: Blockchain TON Halt due to TON network issues
Affected: TON
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are actively blocking the TON network due to TON network issues.
-
identified
The issue has been identified, and we are monitoring the TON network operation status.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB538U: Intermittent delays with incoming UTXO-based transactions
Affected: Bitcoin, Litecoin
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
identified
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
identified
The issue has been identified and a fix is being implemented.
-
identified
We are continuing to work on a fix for this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB537U: Issues with creating vault wallets
Affected: Wallet management
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our wallet infrastructure is currently experiencing an issue that is causing problems with creating vault wallets. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB536U:Transactions and balance updates issues on LTC and BTC blockchain
Affected: Bitcoin, Litecoin
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is experiencing an issue causing problems with finalizing transactions on the LTC and BTC blockchains. Symptoms include transactions failing, outgoing transactions and issues with updating the balance. We are actively investigating this...
-
investigating
We are continuing to investigate this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
identified
We are continuing to work on a fix for this issue.
-
identified
BTC moved to monitoring
-
identified
We are still investigating this issue and will update with further developments
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB535U: Transactions and balance updates issues on Bitcoin blockchain
Affected: Bitcoin
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Bitcoin processing infrastructure is currently experiencing an issue with outgoing and incoming transactions. Symptoms include outgoing transactions stuck on "BROADCASTING" statuses and balance updates. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB534U: Transactions and balance updates issues on the legacy Chiliz blockchain
Affected: Chiliz
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing issues with finalizing transactions on the legacy Chiliz blockchain. Symptoms might be latency with outgoing and incoming transactions and balance updates.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB534U: Blockchain BASE disrupted
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Base mainnet block production is currently unhealthy. We are monitoring the status. For more information, refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB533U: Authentication Issues with Fireblocks console (SSO login only)
Affected: User authentication
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our authentication infrastructure is currently experiencing an issue that is causing login failures for Console users with SSO login. We are currently investigating this issue. Username/Password method works.
-
monitoring
A fix has been implemented and we are monitoring the results. Authentication issues were due to Auth0 status page. Auth0 status page: https://status.auth0.com/incidents/z8sc9m1gzqb7
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB532U: Base Mainnet disruption during Beryl Upgrade
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Base mainnet block production is currently unhealthy. We are monitoring the status. For more information, refer to the Base status page: https://status.base.org/incidents/5c4gm1wzbjs4
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB531U: Transaction Signing delays
Affected: Transactions engine
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating an issue related to transaction signing delays.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB530U: Transactions issues with outgoing transactions
Affected: Transactions engine, API co-signer
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
Our transaction processing infrastructure is currently experiencing an issue which is causing a delay in finalizing the transaction status. Symptoms include delayed notification for transactions approvals on Mobile device and cosigner and also transactions stuck in "Pending...
-
identified
The issue has been identified as part of the transaction serialization, and the fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
monitoring
We are continuing to monitor for any further issues.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB529U: Intermittent delays with XRP transactions
Affected: Ripple
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB528U: Intermittent delays with SUI network outgoing transactions
Affected: SUI
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the outgoing transaction status for SUI network transactions. We are actively investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB527U: Intermittent delays with SUI outgoing transactions
Affected: SUI
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB526U: Issues with login to Fireblocks Console and Transactions
Affected: Transactions engine, Web console
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
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
This incident has been resolved.
-
postmortem
* **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...
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB525U: Intermittent delays with TON transactions
Affected: TON
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
identified
Our 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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB524U: Intermittent delays with updating transaction statuses and balance on Fireblocks console
Affected: Web console
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
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.
-
identified
The issue has been identified and a fix is being implemented.
-
identified
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.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB523U: Transactions and balance updates issues on Kusama blockchain
Affected: Kusama
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
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.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB522U: Intermittent delays with transactions
Affected: Transactions engine
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB521U: Intermittent delays with XRPL network outgoing transactions
Affected: Ripple
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB520U: Delayed Webhook notifications
Affected: Webhooks
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our Webhook(s) processing infrastructure is currently experiencing an issue causing a delay in sending the Webhook(s). We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB520U: Intermittent delays with transactions
Affected: Transactions engine
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB519U: UTXO Chains Degraded Performance
Affected: Bitcoin, Bitcoin Cash, Dogecoin, Litecoin
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
We are currently investigating this issue.
-
investigating
We are continuing to investigate this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB518U: Issues with Ronin blockchain post-migration
Affected: Ronin
Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Ronin Mainnet currently has issues with processing new blocks. We are actively working on our Ronin infrastructure to solve the issue.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB517U: Fireblocks Mobile App approval failures
Affected: Fireblocks mobile app
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Our Mobile notification infrastructure is currently experiencing an issue that is impacting processing of notifications on the mobile application. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB516U: Outgoing transaction issues on Solana blockchain
Affected: Solana
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
investigating
Symptoms include outgoing Solana transactions stuck on "BROADCASTING/SUBMITTED/QUEUED" status or failing with "Internal Fireblocks Error."
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB515U: Intermittent delays with Worldchain network transactions
Affected: WorldChain
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status for Worldchain transactions. We are actively investigating this issue.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on Fireblocks's status page.
FB514U: Litecoin transaction delays during Litecoin chain reorganisation
Affected: Litecoin
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: An external attack. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
investigating
Our transaction processing infrastructure is currently experiencing an issue that is causing a delay in finalizing the transaction status of Litecoin blockchain. We are actively investigating this issue.
-
identified
The issue has been identified and a fix is being implemented.
-
monitoring
A fix has been implemented and we are monitoring the results.
-
resolved
Official disclosure from the Litecoin Foundation - https://x.com/litecoin/status/2048135554445832542 A zero-day vulnerability in Litecoin Core triggered a denial-of-service condition affecting major mining pools. Once the chain stabilised, normal processing resumed. We will...
Excerpts are shortened. Read the full incident on Fireblocks's status page.