Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

Global Financial Service Disruptions

When banks, exchanges, brokers and payment providers unexpectedly stop customers moving money. A restriction is recorded as a fact; its cause is a separate, sourced judgement, and an unexplained restriction is never presented as an attack.

Analyst assessment, Nov 5Status: ElevatedTrend: Insufficient evidenceEvidence confidence: Low

On a fixed panel of 54 provider status feeds, restrictions rose from 48 to 58 between the two most recent 14-day windows, within normal variation. What changed is the cause mix: nine restrictions with confirmed cyber causes began in the last 14 days against one in the 14 days before, led by the Binance withdrawal freeze, Credit Mutuel Arkea and a Japanese hosting breach that reached FX brokers. Historical coverage is too uneven to call a multi-year acceleration.

Verified restrictions on record
4
Research register, 2022 to now
Countries
1
With at least one record
Confirmed cyber cause
0
Of all verified records
Still restricted
0
Active or recovering
Last 14 days, verified
2 vs 2
Against the 14 days before (search effort differs)
Last 14 days, provider-posted
119
Status-feed watcher; last pass Nov 6 22:35 UTC

Where restrictions were recorded

Countries shaded by number of verified records; select one to filter. Red dot: confirmed cyber cause. Open amber ring: unexplained. Grey: other causes. Counts reflect where DFX searched as much as where events happened.

Live: provider-posted restrictions

Raised automatically when a financial provider's own status page says customers cannot withdraw, deposit, transfer, settle or trade. Unclassified until an analyst reviews them; hand-checked precision of the rule on 30 posts was 87%.

Coverage is reduced: DFX is not reading 105 of 124 status feeds, because their robots.txt does not allow it or could not be read, while we move to the incident feeds providers publish.

  • FlutterwaveNov 6 06:56 UTC · payment processor
    Cause not yet classifiedcard authresolved

    [NGN] Service Alert: Intermittent Card Transaction Failures

  • XenditNov 6 06:40 UTC · payment processor
    Cause not yet classifiedpayoutsresolved

    Payouts Disruption in Indonesia

  • FlutterwaveNov 5 22:19 UTC · payment processor
    Cause not yet classifiedpayoutsactive

    [NGN] Service Alert: Pending Payouts on Flutterwave for Business (F4B)

  • XenditNov 5 21:50 UTC · payment processor
    Cause not yet classifieddeposits0 h

    EWALLET TRUEMONEY Thailand Disruption

  • XenditNov 5 21:30 UTC · payment processor
    Cause not yet classifiedpayoutsresolved

    Payouts Disruption in Indonesia

  • FlutterwaveNov 5 18:15 UTC · payment processor
    Cause not yet classifiedcard authresolved

    Service Alert: BIN Service Disruption – Impact on Card Transactions

  • XenditNov 5 17:10 UTC · payment processor
    Cause not yet classifiedpayoutsresolved

    Payouts Disruption in Philippines

  • XenditNov 5 15:30 UTC · payment processor
    Cause not yet classifiedtransferspayoutsresolved

    Payouts Disruption in Indonesia

  • CurrencycloudNov 5 14:39 UTC · payment processor
    Cause not yet classifiedpayoutsresolved

    Potential delays to funding

  • FlutterwaveNov 5 14:09 UTC · payment processor
    Cause not yet classifiedtransfersresolved

    [NGN] Service Alert: Intermittent Name Enquiry Failures

  • ToastNov 5 10:47 UTC · payment processor
    Cause not yet classifieddepositsresolved

    Deposit Delay

  • KrakenNov 5 10:19 UTC · crypto exchange
    Cause not yet classifiedwithdrawalsdepositspayoutsactive

    Deposit and Withdrawal Delays on Multiple Networks

  • XenditNov 5 07:50 UTC · payment processor
    Cause not yet classifiedpayouts0.2 h

    Payouts Disruption in Philippines

  • XenditNov 5 05:37 UTC · payment processor
    Cause not yet classifieddeposits0.3 h

    QR_CODE XENDIT Indonesia Disruption

  • XenditNov 5 05:37 UTC · payment processor
    Cause not yet classifieddeposits0.3 h

    EWALLET DANA Indonesia Disruption

Active restriction tracker

Verified restrictions not yet reported as fully restored.

    Verified significant restrictions by month

    Tier 1 research records (broad, unexpected, an hour or more or reported by a regulator or credible outlet). Red is the confirmed-cyber share. Search depth was much greater for October 2026 than for earlier months, so this chart cannot show acceleration on its own.

    2026-10: 2 recorded, 0 confirmed cyber

    Early-warning watchlist: unexplained restrictions

    Verified restrictions from the last 45 days with no established cause. Listed because the cause is unknown, not because an attack is suspected.

    • Flutterwave KES payout provider (unnamed)Nov 3 · KE · payment processor
      Unexplainedpayoutsresolved

      Flutterwave reported two separate KES payout interruptions on 3 Nov 2026 (resolved by 06:55 and 11:54 UTC) in which payouts were delayed or did not reach recipients.

    • Safaricom M-PESAOct 27 23:00 UTC · KE · fintech
      Unexplainedtransfers outpayoutsallunknown

      M-PESA services were disrupted across Kenya from about 02:00 EAT on 28 Oct 2026, blocking send-money, airtime and bill payments. Safaricom apologised and said teams were restoring service; no cause or restoration time found.

    • KCB M-PESAOct 19 · KE · commercial bank
      Unexplainedwithdrawalsdepositstransfers outtransfers inunknown

      KCB M-PESA suffered repeated unplanned interruptions from 19 to 22 Oct 2026 that Safaricom attributed to a system issue, with some customers' withdrawals debited but not credited for up to 48 hours. A separately announced maintenance...

    • M-PESA (as listed by Paystack under Ghana)Oct 11 20:51 UTC · KE · fintech
      Unexplaineddeposits4.27 h

      Paystack logged most M-PESA mobile money payments failing for about four hours overnight 11 to 12 Oct 2026, under a 'Ghana' title.

    Shared infrastructure

    Providers named in two or more verified records. A shared provider is a documented dependency, not evidence of a shared compromise.

    No provider is named in more than one record yet.

    Case library

    Tier 1 restrictions of severity 4 or 5, newest first.