Kraken, Paystack and Kora reported five service disruptions affecting cryptocurrency transfers, US futures trading, bank payments and African payout corridors between October 29 and November 1. In today’s payment and crypto infrastructure roundup, Kraken’s US futures maintenance remained open for more than 14 hours against a planned two-hour window, Paystack recorded 37 hours of Nigerian bank-transfer disruption, and Kora resolved separate problems involving Egyptian pound payouts and Orange Money transactions. Kraken also restored Flow cryptocurrency funding after a 30-hour incident.
All five incidents have been marked resolved in their respective status records. The published durations establish how long each incident remained recorded, although they do not necessarily represent continuous service unavailability throughout those periods.
Kraken’s two-hour futures maintenance stretches past 14 hours
Kraken’s scheduled US futures maintenance ran for 14 hours and 31 minutes according to its official status timestamps, more than seven times the maximum duration initially announced to customers.
The exchange notified users on October 29 that its US futures execution provider would conduct maintenance beginning at 23:30 UTC on October 30, with work expected to last up to two hours.
Kraken marked the maintenance as underway at the scheduled starting time but did not publish its completion notice until 14:01 UTC on October 31. The difference between the initial two-hour allowance and the recorded completion time was 12 hours and 31 minutes.
Two hours was the plan, and the recorded maintenance window went much longer than that.
The work covered Kraken’s US derivatives infrastructure, including CME Group 24/7 futures products and Bitnomial perpetual futures listed in the announcement. Kraken warned that customers would be unable to place, modify, cancel or close orders and positions during maintenance, including through its application programming interfaces.
Market data could also be affected. The exchange recommended that clients close positions or cancel working orders they did not wish to retain during the maintenance period. Non-US linear multi-collateral derivatives and other products were excluded from the scheduled work.
The longer-than-planned record does not establish that every affected trading function remained unavailable for the full 14 hours and 31 minutes. Kraken did not publish intermediate restoration timestamps or an explanation for the extended period between the scheduled start and final completion update.
The episode follows a previous Kraken futures maintenance event involving NinjaTrader infrastructure on September 18 and 19. That earlier scheduled window lasted approximately two and a half hours and similarly restricted customers’ ability to manage existing futures positions.
For leveraged traders, the operational question concerns whether orders could actually be adjusted during the extra hours shown in the latest record. The published status history does not provide the transaction-level evidence necessary to establish that.
Kraken restores FLOW deposits and withdrawals after 30 hours
Kraken also resolved a seperate funding incident affecting Flow (FLOW) deposits and withdrawals, which remained recorded for approximately 30 hours and 23 minutes.
The exchange opened an investigation at 22:20 UTC on October 29, warning that transactions involving the FLOW funding gateway could experience delays. It stated that other cryptocurrency funding methods were operating normally.
On October 30 at 22:31 UTC, Kraken said a fix had been implemented and moved the incident into monitoring. The final resolution notice followed at 04:43 UTC on October 31.
The correction was announced roughly 24 hours after the original report, but formal resolution came another six hours later. Recovery and final confirmation were not quite the same point in time.
Kraken did not identify the technical root cause, disclose how many deposits or withdrawals were affected, or specify whether any transactions required manual processing.
The FLOW problem was distinct from the futures maintenance. One involved a cryptocurrency funding gateway; the other concerned an execution provider supporting US derivatives trading.
The funding interruption also followed earlier Kraken funding problems involving the Plasma and Sui networks reported on October 27 and 28. Those incidents concerned different blockchain integrations and do not establish a shared underlying failure.
Across these cases, Kraken’s public notices identify affected products and restoration milestones but provide limited information about the technical failures or the volume of delayed transfers.
Paystack’s Nigerian bank-transfer incident lasts 37 hours
Paystack recorded a major disruption to Nigerian bank transfers that began at 20:16 UTC on October 30 and was officially resolved at 09:20 UTC on November 1, a period of 37 hours and four minutes.
The payments company attributed the initial problem to downtime involving Nigeria’s Central Switch, reporting increased failures across incoming Pay with Transfer transactions, Dedicated Virtual Accounts and outgoing bank transfers.
Merchants receiving payments into Paystack-managed virtual accounts could encounter failed or delayed transactions. Outbound transfers to bank accounts were also affected.
At 09:40 UTC on October 31, Paystack reported improved central-switch processing and said transfers were succeeding again. A subsequent update at 09:43 UTC confirmed that Managed Accounts and bank transfers were processing while the company continued monitoring recovery.
That put the first reported improvement approximately 13 hours and 24 minutes after the incident began, substantially earlier than its final resolution the following day.
Paystack advised that pending transfers would update automatically after confirmation. It did not disclose the number of delayed payments, their monetary value or how many remained unresolved when processing first improved. No transaction-level breakdown was made availble.
The reliance on switching infrastructure is consistent with Nigeria’s payment-system architecture. The Central Bank of Nigeria’s payments-system overview identifies the National Central Switch as part of the country’s electronic payment infrastructure and documents the regulatory framework governing payment switching.
Paystack’s incident notice attributed the transfer failures to central-switch downtime but did not identify how many other institutions or payment providers experienced related problems.
A second, shorter incident affected Nigerian-issued card payments on October 31. Paystack reported elevated card-transaction failures at 11:47 UTC because of downstream processor downtime, before moving the incident into monitoring at 12:41 UTC.
The card issue was resolved at 14:09 UTC, with the status platform recording approximately two hours and 21 minutes of disruption. Paystack treated the card-processing problem separately from the bank-transfer incident and did not identify a common cause.
Earlier in October, Paystack and PawaPay reported disruptions linked to Telecel Ghana, where the same mobile-money operator affected multiple payment intermediaries. In the latest Nigerian incident, comparable independent confirmation of central-switch disruption across other providers was not established in the reviewed records.
Paystack has not published a detailed account of any reconciliation work or outstanding merchant balances arising from the extended incident.
Kora resolves Egyptian pound and Orange Money disruptions
African payment infrastructure provider Kora recorded two separate service problems across its payment corridors, including a six-hour disruption to Egyptian pound payouts and nearly 48 hours of degraded Orange Money transactions.
On October 30 at 13:23 UTC, Kora reported instability in its EGP payout channel and classified the incident as a major outage.
Its technical team investigated the problem before announcing restoration at 19:50 UTC, giving the incident a recorded duration of six hours and 27 minutes.
The payout instability followed an earlier scheduled maintenance window affecting the same currency. Kora had planned four hours of EGP system work beginning at 20:30 UTC on October 29, citing daylight-saving adjustments.
The maintenance was recorded as successfully completed at 00:30 UTC on October 30, almost 13 hours before the later payout problem was reported.
The timing sits close enough to invite a comparison, but Kora has not said the two events were connected.
The company did not provide a root-cause report identifying whether the payout instability originated within its own infrastructure, a banking partner or another intermediary. It also did not disclose the number of merchants affected, the value of pending payouts or whether any settlements required additional processing.
In a separate incident, Kora reported degraded Orange Money performance beginning at 13:49 UTC on October 29. The incident was classified under its Central African franc (XAF) corridor and marked resolved at 13:45 UTC on October 31, with a recorded duration of approximately 47 hours and 55 minutes.
Kora attributed the technical work to Orange, stating that the mobile-money operator’s team was investigating the instability. Its final notice confirmed that Orange transactions had resumed normal processing.
The incident history contains a geographic inconsistency. One notice identifies the XAF corridor, while another entry carrying the same opening timestamp refers to the West African franc (XOF) corridor. The status component itself lists XAF.
It is not fully clear from those notices just how far the Orange disruption extended geographically.
The XAF and XOF corridors serve different African monetary zones, so the conflicting descriptions prevent a precise determination of whether the incident affected only Central African markets or also involved West African transactions.
The status record describes degraded performance rather than a complete outage. Kora did not publish transaction success rates, the individual Orange markets affected or the total value of unsuccessfull payments.
Both Kora incidents were resolved by October 31, and its status dashboard subsequently reported normal operations. The company has not published a detailed explanation connecting the EGP problem to the earlier maintenance or clarifying the Orange Money corridor discrepancy.
Across the five incidents, the most substantial unresolved questions concern Kraken’s actual order-execution downtime, Paystack’s pending-transfer reconciliation and the geographic extent of Kora’s Orange Money disruption. The recorded restoration times are confirmed, but the full operational and financial impact remains unquantified in the public disclosures.
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