Kraken Resolves XPL and USDC Delays as SUI Fix Advances

The three cases illustrate how individual blockchain integrations can experience operational problems independently, potentially delaying customers’ access to assets even when an exchange’s wider services remain available. Kraken’s official status history confirms that the Plasma incident lasted approximately 24 hours from its initial report, while the USDC-on-ARC disruption was resolved in less than two hours.

The exchange has not disclosed the underlying technical causes, the number of affected customers, the volume of delayed transactions or any financial losses associated with these incidents.

Kraken Resolves Plasma Funding Delays After 24 Hours

Kraken first reported an issue affecting its Plasma (XPL) funding gateway on October 27 at 15:34 UTC, warning that deposits and withdrawals could be delayed while its technical team investigated.

According to the exchange’s official status history, Kraken implemented a fix at 10:11 UTC on October 28 and moved the incident into monitoring. It subsequently marked the problem resolved at 15:55 UTC that day.

The interval between the initial report and the resolution announcement was approximately 24 hours and 21 minutes. The monitoring period following implementation of the fix lasted another five hours and 44 minutes.

Kraken did not provide a technical explanation for the failure or identify a specific component responsible for the disruption. Its notice stated that other funding methods continued to operate normally while the Plasma gateway was affected.

The distinction between a funding gateway and a blockchain network is important. Kraken’s announcement establishes that the exchange experienced difficulties processing XPL deposits and withdrawals; it does not establish that the Plasma network itself suffered an outage.

For customers, a funding delay can create practical problems even when the asset remains tradable. A trader expecting to deposit XPL before executing a strategy may miss an opportunity, while someone attempting to withdraw tokens may be unable to move them to a personal wallet or another trading venue within the expected timeframe.

These restrictions can also complicate arbitrage. Traders who rely on moving assets between exchanges to exploit price differences need reliable deposit and withdrawal channels. When one venue’s gateway becomes unavailable, the ability to act on price discrepancies may be reduced.

Kraken’s resolution announcement indicates that the exchange considered the incident resolved, but it does not quantify the number of delayed transfers subsequently processed or establish whether any customers incurred measurable losses.

USDC on ARC Returns to Normal After Brief Disruption

A separate incident affected USD Coin transfers on the ARC network during the early hours of October 28.

Kraken reported the problem at 02:34 UTC, stating that deposits and withdrawals for USDC on ARC could be delayed. The exchange announced that a fix had been implemented at 04:10 UTC and marked the incident resolved at 04:14 UTC.

The total interval between the initial notice and resolution was one hour and 40 minutes. The monitoring phase lasted just four minutes before Kraken published its resolution update.

The incident was specifically associated with the USDC funding gateway on ARC. It should not be interpreted as evidence that USDC transfers were disrupted across every supported blockchain network or that the stablecoin itself experienced a loss of its dollar peg.

USDC operates across multiple blockchain networks, and exchange customers must select a supported network when depositing or withdrawing the asset. A problem affecting one network’s funding integration can therefore restrict transfers through that route without necessarily affecting other USDC funding methods.

Kraken’s notice said other funding methods remained operational. However, the exchange did not identify the technical cause of the ARC issue or disclose how many transfers were delayed.

The relatively short resolution window suggests that Kraken restored the affected service quickly, but the available record does not establish whether the problem originated in the exchange’s own infrastructure, its network integration or another component of the transaction-processing process.

For customers, the immediate concern is whether pending transfers were processed successfully after the fix. A resolved status indicates that the reported service problem has been addressed, but it does not provide transaction-by-transaction confirmation for individual accounts.

SUI Funding Incident Remains Under Monitoring

Kraken’s SUI funding issue followed a longer and less straightforward timeline. The exchange initially reported delays affecting SUI deposits and withdrawals on October 26 at 09:39 UTC.

The status history subsequently recorded an identified issue and a planned fix at 14:21 UTC that day, followed by a monitoring update at 07:19 UTC on October 27. Kraken then reported another identified issue at 11:00 UTC on October 27.

On October 28 at 10:54 UTC, Kraken issued another update stating that a fix had been implemented and that the results were being monitored.

Unlike the Plasma and USDC-on-ARC incidents, the latest SUI entry did not mark the incident resolved. The distinction matters because a fix entering monitoring is not the same as a confirmed return to normal operations.

The repeated updates also show why incident timelines need to be read carefully. An earlier fix or monitoring announcement does not necessarily mean the problem has been permanently eliminated, particularly when a subsequent update indicates that further corrective work was required.

Kraken has not explained why the SUI issue required repeated interventions, whether the successive updates concerned the same underlying fault or how many customers experienced delayed transfers.

The exchange again indicated that other funding methods remained operational, limiting the reported disruption to the affected funding route rather than its entire cryptocurrency platform.

What the Incidents Mean for Kraken Customers

Viewed together, the three incidents highlight the operational complexity of supporting cryptocurrency deposits and withdrawals across multiple networks and assets.

Even when an exchange’s main trading services remain available, individual funding integrations can prevent customers from moving assets on schedule. That separation is particularly important for active traders, arbitrage strategies and businesses that depend on predictable settlement and transfer times.

The Plasma incident is notable for its duration. More than 24 hours elapsed between Kraken’s initial notice and its final resolution update, creating a potentially significant period of uncertainty for customers relying on the XPL funding gateway.

The USDC-on-ARC incident was substantially shorter, but it illustrates the importance of network-specific support. Customers cannot assume that a stablecoin’s availability on one blockchain guarantees uninterrupted transfers through another.

The SUI case warrants continued attention because the latest status update confirmed monitoring rather than final resolution. The next meaningful development would be an explicit closure notice or further information explaining whether the corrective measures restored reliable funding operations.

There is no evidence in the published notices that the three incidents were connected, caused by a security breach or resulted in confirmed customer losses. Their proximity in time alone does not establish a common technical cause.

For affected customers, the practical steps are to check Kraken’s current funding status, verify the selected asset and network, and review individual transaction records before assuming that a delayed transfer has failed or been lost. Customers should avoid repeatedly initiating transfers without first establishing the status of pending transactions.

For market observers, the key indicators are whether the resolved gateways remain stable, whether Kraken closes the SUI incident and whether the exchange publishes additional information about the causes or customer impact.

Ultimately, the announcements document three separate operational disruptions with different timelines and outcomes. Plasma and USDC on ARC were marked resolved on October 28, while SUI remained under monitoring. That distinction provides a clearer picture of the exchange’s response than treating every funding delay as either a confirmed loss or a fully resolved problem.