Kraken’s Tezos (XTZ) funding channel suffered multi-day delays in deposits and withdrawals after the cryptocurrency exchange identified a problem on October 22 and implemented a fix the following day. The issue was confined to the processing of a particular digital asset rather than a reported exchange-wide outage, but it illustrates how a customer’s ability to move crypto can remain uncertain even while the rest of a trading platform appears operational.
Kraken’s official status feed recorded the Tezos incident at 17:04 UTC on October 22, saying the company was experiencing delays in both incoming and outgoing XTZ transfers. At 14:47 UTC on October 23, it moved the incident to monitoring after implementing a fix. A research lead dated October 26 describes the case as resolved, but the accessible status-feed text reviewed for this article did not independently show a final October 26 resolution timestamp; the page’s Tezos component was displayed as operational. That distinction prevents a precise claim about the moment the incident formally closed.
The exchange has not published a customer count, number of delayed transfers, value of XTZ awaiting processing or evidence of resulting customer losses. The available notice also gives no technical root cause. Those gaps limit conclusions about the operational severity beyond the confirmed funding delays.
What Happened to Kraken’s Tezos Deposits and Withdrawals?
Kraken’s official service-status page identified the issue as “Tezos (XTZ) Funding Delays.” The original announcement at 17:04 UTC on October 22 said that deposits and withdrawals were delayed and that staff were working on a resolution. Its later update at 14:47 UTC on October 23 said a fix had been implemented and results were being monitored.
Those updates establish at least 21 hours and 43 minutes from the first published identification to the implementation of the fix. They do not necessarily measure how long any individual customer waited: a transfer could have begun processing before Kraken posted the alert, or it could have cleared after the fix while the exchange continued monitoring.
The October 26 summary describes a four-day incident window. That may reflect the time between the opening notice and a later closure, but a formal closure timestamp could not be verified in the publicly accessible status text. The safest interpretation is a disruption that originated on October 22, received a fix October 23 and remained under post-fix scrutiny afterward.
Kraken’s reported problem applied specifically to XTZ funding. There was no corresponding statement that trading engines, fiat payments, Bitcoin withdrawals or every cryptocurrency funding route had failed as part of the same incident. A broad label such as “Kraken withdrawals halted” would therefore overstate the evidence.
Why Can a Deposit Be Delayed Even When a Blockchain Works?
A cryptocurrency transfer has at least two distinct stages: confirmation on the underlying blockchain and recognition or release by the custodian or exchange. An XTZ transaction may be broadcast and included on the Tezos chain without appearing immediately as available funds in a Kraken account if the exchange’s crediting infrastructure is experiencing difficulties.
An outgoing transfer creates a similar distinction. A user can submit a withdrawal request on the exchange, but the exchange must approve and construct the blockchain transaction, apply relevant checks and broadcast it. If that workflow is delayed, the user may see the withdrawal as pending even though the broader network is operating normally.
This is a general description of custody architecture, not a diagnosis of the October incident. Kraken did not identify whether the underlying problem involved its Tezos node, confirmations policy, internal ledger, wallet operations, a software deployment or some other factor.
That separation was relevant in DaveFinances’ examination of transfers to outdated exchange deposit addresses, where on-chain delivery and exchange crediting can also diverge. It does not mean Kraken’s Tezos delays were caused by an address change.
Users checking an affected transfer would need to distinguish a withdrawal that has not received a transaction hash from a transaction already visible on a Tezos block explorer. Both can appear as delays to the user, yet troubleshooting and recovery options differ.
Did the Incident Put Customer Funds at Risk?
Nothing in the confirmed October 22 and October 23 notices establishes a hack, missing customer tokens, unauthorized access or an insolvency problem. Funding delays, while disruptive, do not by themselves mean that a user’s underlying cryptocurrency was stolen or lost.
Nor does the absence of a reported loss prove that no customer experienced harm. Someone waiting for an XTZ deposit to reach the trading account could miss a trading opportunity, while a delayed withdrawal could prevent a planned transfer or participation in an on-chain application. Quantifying those effects would require individual transaction records and user evidence not provided in the status announcement.
Kraken has previously experienced separate payment and transfer disruptions, including an incident that disrupted card and instant-buy transactions and temporarily withheld some users’ available funds. The comparison shows that different services inside one exchange can fail independently; it does not establish that the two incidents shared a cause.
Similarly, Coinbase’s Canadian Interac withdrawal delays affected a different payment channel. The recurring operational lesson is that access to an account or an active trading screen is not proof that every funding pathway is processing normally.
What Does a Fix Followed by Monitoring Actually Tell Customers?
When a status page moves from identified to monitoring, the operator is usually indicating that an intervention has been deployed and that staff are looking for evidence the service is behaving normally. It is not automatically the same as a completed incident report or proof that every transfer in an earlier backlog has settled.
Conversely, an asset component marked operational in a status dashboard is evidence of the operator’s present service assessment, not a per-user guarantee. A previously delayed deposit may still require account-specific investigation. The accessible Kraken page displayed XTZ as operational, while the incident timeline available in the indexed status text stopped at monitoring.
That ambiguity matters for independent reporting. A news article can establish the date the issue was identified and the time of the fix without inventing a precise duration or resolution moment. If a later official closure notice becomes available, the timeline can be updated with its actual UTC timestamp.
Users with pending XTZ transfers should preserve the destination address, transaction hash if one exists, transfer amount and request time. Duplicate withdrawals or repeated deposits are not a reliable way to bypass a processing backlog and can create additional reconciliation questions.
What Should Exchange Customers and Investors Watch Next?
The most useful follow-up from Kraken would specify whether the issue arose inside its custody infrastructure or from an external Tezos dependency, how many transactions were delayed, whether backlogged deposits and withdrawals were fully processed, and when the incident was formally closed.
For customers, these are practical reliability metrics. A service that is technically available most of the time can still be hard to use if transfers are intermittently delayed at the moment when an investor needs funds for collateral or settlement. Exchange-wide uptime statistics may conceal problems concentrated in a single asset.
For the market, the event should not be exaggerated into evidence of a Tezos network-wide breakdown or a major Kraken solvency event. The confirmed development is narrower: XTZ transfers were delayed from October 22, a fix was reported October 23, and the accessible public notices do not quantify financial harm or independently fix a final resolution timestamp.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574